← previous blocknext block →recent activity
Analyzing
Block #72,310,834
10 transactions · 9 stateful · 2026-05-04 05:13:08 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,310,834 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x499adbcf…eb20
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a7
0x8d66a4…3095
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
3 touches
1 conflict
0x6fdc73d3…9853
0x8d66a4…3095
3 touches
1 conflict
0x8a35acfb…d1ae
0x8d66a4…3095
3 touches
1 conflict
0x3254d19b…f714
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
1 conflict on slot 0x499adbcfeb…b6eb20
Audit this contract →
← previous block·next block →recent activity