← previous blocknext block →recent activity
Analyzing
Block #81,633,425
14 transactions · 7 stateful · 2026-06-16 09:35:08 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,633,425 · 14 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x47501790…1682
0x065c9d…c394
3 touches
1 conflict
0xf0504c32…8e1c
0x065c9d…c394
3 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
2 touches
0 conflicts
0x5df2f472…536a
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
2 touches
0 conflicts
0x00000000…0000
0x8ff385…ce4a
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity