← previous blocknext block →recent activity
Analyzing
Block #80,167,418
15 transactions · 9 stateful · 2026-06-09 14:44:43 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,167,418 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x82ec1892…68af
0x065c9d…c394
4 touches
1 conflict
0xb7c8652f…ebce
0x1111b3…4111
2 touches
0 conflicts
0x00000000…000d
0x7197e2…4e53
2 touches
0 conflicts
0x405787fa…dd36
0x7197e2…4e53
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity