← previous blocknext block →recent activity
Analyzing
Block #72,928,911
18 transactions · 17 stateful · 2026-05-07 01:51:31 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,928,911 · 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
1w04w05w110w114w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e66da19…66b6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0x032c41ac…c35a
0x065c9d…c394
4 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
4 touches
1 conflict
0x4e5ebbf7…ae70
0xc8689a…ee79
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x6ca43f…c331
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x8e66da1932…c966b6
Audit this contract →
← previous block·next block →recent activity