← previous blocknext block →recent activity
Analyzing
Block #72,928,878
19 transactions · 16 stateful · 2026-05-07 01:51:18 UTC
Parallelism
74/100
Blocked
31%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,928,878 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w112w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e66da19…66b6
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x634fbfb3…1843
0x065c9d…c394
4 touches
1 conflict
0x71c854be…16cb
0x065c9d…c394
4 touches
1 conflict
0x9f856c4f…6f34
0x065c9d…c394
4 touches
1 conflict
0xf72845f2…6d44
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0x8e66da1932…c966b6
Audit this contract →
← previous block·next block →recent activity