← previous blocknext block →recent activity
Analyzing
Block #72,209,854
40 transactions · 30 stateful · 2026-05-03 17:55:26 UTC
Parallelism
88/100
Blocked
60%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,209,854 · 40 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w07w18w09w113w214w115w016w117w219w020w121w122w223w326w027w128w229w130w233w336w237w338w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02838a3…bc54
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x41755291…977f
0x065c9d…c394
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0003
0x63e48b…53f2
6 touches
3 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: Perpl
10 conflicts on slot 0xa02838a385…ffbc54
Audit this contract →
← previous block·next block →recent activity