← previous blocknext block →recent activity

Analyzing

Block #72,209,060

12 transactions · 11 stateful · 2026-05-03 17:50:04 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,209,060  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x8a35acfb…d1ab

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0xe72962f6…e169

0x8d66a4…3095

4 touches
1 conflict

0x28e259b6…8e20

0x065c9d…c394

2 touches
0 conflicts

0x3bc444cc…88da

0x065c9d…c394

2 touches
0 conflicts

0x58c3fa11…19e5

0x065c9d…c394

2 touches
0 conflicts

0x5ef20b9e…eb9b

0x065c9d…c394

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: 0x8d66a43f…113095

3 conflicts on slot 0x8a35acfbc1…6bd1ab

← previous block·next block →recent activity