← previous blocknext block →recent activity
Analyzing
Block #72,310,888
12 transactions · 12 stateful · 2026-05-04 05:13:30 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,310,888 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w37w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99f080dc…58c1
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x908d4442…2c4b
0x34b655…2a6f
8 touches
6 conflicts
0x475d29e4…3caf
0x34b655…2a6f
6 touches
3 conflicts
0x5728edaf…f1d4
0x34b655…2a6f
6 touches
3 conflicts
0x578e7f66…1b56
0x34b655…2a6f
6 touches
3 conflicts
0x57de3828…3fbb
0x34b655…2a6f
6 touches
3 conflicts
0xc6417de0…2191
0xc8689a…ee79
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
6 conflicts on slot 0x99f080dc2c…dd58c1
Audit this contract →
← previous block·next block →recent activity