← previous blocknext block →recent activity
Analyzing
Block #84,459,312
8 transactions · 8 stateful · 2026-06-29 11:54:09 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,459,312 · 8 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…0006
0x2ab50b…5c41
2 touches
0 conflicts
0x2ad9a0a3…84ba
0x2ab50b…5c41
2 touches
0 conflicts
0x32d6f0f9…c4be
0x2ab50b…5c41
2 touches
0 conflicts
0x38565799…ea68
0x2ab50b…5c41
2 touches
0 conflicts
0x3a9d4ba4…0a37
0x2ab50b…5c41
2 touches
0 conflicts
0x42ecd855…0611
0x2ab50b…5c41
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