← previous blocknext block →recent activity
Analyzing
Block #72,285,350
18 transactions · 11 stateful · 2026-05-04 02:22:47 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,285,350 · 18 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
1w02w13w26w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
6 touches
3 conflicts
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0xcc6521c1…c892
0x8d66a4…3095
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
2 touches
0 conflicts
0x6c6bef2a…6bdf
0x34b655…2a6f
2 touches
0 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity