← previous blocknext block →recent activity
Analyzing
Block #72,271,218
11 transactions · 11 stateful · 2026-05-04 00:47:48 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,271,218 · 11 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
1w02w07w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xae7c69bf…0168
0x065c9d…c394
4 touches
1 conflict
0x47cebe7d…b7d3
0x065c9d…c394
3 touches
1 conflict
0x3a1dd761…6cab
0x065c9d…c394
3 touches
1 conflict
0x833794a3…7020
0x065c9d…c394
2 touches
0 conflicts
0xc6d91b76…a590
0x065c9d…c394
2 touches
0 conflicts
0xef138727…06f1
0x065c9d…c394
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: 0x681e908b…e1ae09
3 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity