← previous blocknext block →recent activity
Analyzing
Block #72,431,212
18 transactions · 17 stateful · 2026-05-04 18:35:10 UTC
Parallelism
61/100
Blocked
65%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,431,212 · 18 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
1w04w05w16w27w38w49w511w112w213w115w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1ad
0x8d66a4…3095
8 touches
6 conflicts
0x13b1d959…1c28
0x34b655…2a6f
6 touches
3 conflicts
0x2343b4c2…d6bb
0x34b655…2a6f
6 touches
3 conflicts
0x3c35979a…975d
0x34b655…2a6f
6 touches
3 conflicts
0x414e9446…4b59
0x34b655…2a6f
6 touches
3 conflicts
0x65e795ca…0320
0x34b655…2a6f
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity