Block #71,743,113

← previous blocknext block →recent activity

Analyzing

Block #71,743,113

12 transactions · 7 stateful · 2026-05-01 14:05:28 UTC

Parallelism

83/100

Blocked

14%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,743,113  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x6254f674…face

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x265ae30e…da33

0x065c9d…c394

3 touches
1 conflict

0x4e56b607…e8cf

0x065c9d…c394

3 touches
1 conflict

0x4c93193c…f061

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xbc705119…541d

0x065c9d…c394

2 touches
0 conflicts

0xd74d5bed…5e7e

0x2a68ba…90c5

2 touches
0 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x065c9d28…a9c394

1 conflict on slot 0x6254f6749d…89face

← previous block·next block →recent activity