← previous blocknext block →recent activity
Analyzing
Block #72,972,505
23 transactions · 20 stateful · 2026-05-07 06:41:30 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,972,505 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w010w111w215w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x91f75f09…edc1
0xd32edf…ff58
7 touches
6 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0xad882ea4…7ac7
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x67db7ce4…4a60
0x065c9d…c394
5 touches
3 conflicts
0xa69f6e58…ea5a
0x065c9d…c394
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity