← previous blocknext block →recent activity
Analyzing
Block #72,978,864
10 transactions · 8 stateful · 2026-05-07 07:23:50 UTC
Parallelism
70/100
Blocked
25%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,978,864 · 10 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x00000000…0005
0x1397bd…f779
2 touches
0 conflicts
0x0f44ce3c…7e23
0x350035…7777
2 touches
0 conflicts
0x64dc853a…9f58
0x350035…7777
2 touches
0 conflicts
0xf4c2691d…a7d9
0x350035…7777
2 touches
0 conflicts
0x0983b8c8…4d94
0x3bd359…433a
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity