← previous blocknext block →recent activity

Analyzing

Block #72,400,264

11 transactions · 10 stateful · 2026-05-04 15:08:59 UTC

Parallelism

82/100

Blocked

20%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,400,264  ·  11 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

0xe6614ed0…e5fb

0x065c9d…c394

4 touches
1 conflict

0xc079cc93…b57b

0xea1b8e…c5ec

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x1728ed63…499c

0xea1b8e…c5ec

4 touches
1 conflict

0x2709583c…f5f5

0x065c9d…c394

3 touches
1 conflict

0x5814ff3a…6615

0x065c9d…c394

3 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x00000000…010d

0xd45826…f134

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 0xe6614ed0e8…25e5fb

← previous block·next block →recent activity