← previous blocknext block →recent activity
Analyzing
Block #72,817,617
19 transactions · 17 stateful · 2026-05-06 13:30:06 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,817,617 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w19w010w111w215w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x9b0235a2…a1dc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0xeebd31ac…0794
0x34b655…2a6f
4 touches
1 conflict
0x6d0c65d9…c36f
0x34b655…2a6f
4 touches
1 conflict
0x757254ae…d917
0x34b655…2a6f
4 touches
1 conflict
0x7b97d40a…09ed
0x34b655…2a6f
4 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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity