← previous blocknext block →recent activity
Analyzing
Block #84,112,542
12 transactions · 10 stateful · 2026-06-27 21:23:55 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,112,542 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x949ff6d2…0210
0x065c9d…c394
4 touches
1 conflict
0x6776f7f5…1f88
0x065c9d…c394
4 touches
1 conflict
0x3b500c93…b526
0x065c9d…c394
3 touches
1 conflict
0xdf39fa2c…fe42
0x065c9d…c394
3 touches
1 conflict
0x68f23560…2e21
0x065c9d…c394
3 touches
1 conflict
0x132a9482…9227
0x065c9d…c394
3 touches
1 conflict
0x5b571ba0…f13a
0x98dc6e…8633
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