← previous blocknext block →recent activity

Analyzing

Block #72,399,130

12 transactions · 8 stateful · 2026-05-04 15:01:25 UTC

Parallelism

83/100

Blocked

13%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,399,130  ·  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

0x639f478c…ed77

0x065c9d…c394

4 touches
1 conflict

0x1c6ecbfb…ee06

0x065c9d…c394

4 touches
1 conflict

0x800ac136…0d72

0x065c9d…c394

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb0e7066f…fb59

0x065c9d…c394

3 touches
1 conflict

0xf3a6433d…02e7

0x065c9d…c394

3 touches
1 conflict

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 0x639f478c39…6fed77

← previous block·next block →recent activity