← previous blocknext block →recent activity
Analyzing
Block #72,287,791
16 transactions · 11 stateful · 2026-05-04 02:39:13 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,287,791 · 16 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
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x50c2960c…5f37
0x34b655…2a6f
4 touches
1 conflict
0x52569b6c…6f31
0x34b655…2a6f
4 touches
1 conflict
0x539a9d81…8208
0x34b655…2a6f
4 touches
1 conflict
0x5be76e36…362d
0x34b655…2a6f
4 touches
1 conflict
0x676b5eb4…0b33
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity