← previous blocknext block →recent activity
Analyzing
Block #84,199,611
21 transactions · 21 stateful · 2026-06-28 07:03:27 UTC
Parallelism
86/100
Blocked
19%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,199,611 · 21 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
1w02w110w012w013w014w115w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0001
0x8b0d32…7367
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity