← previous blocknext block →recent activity
Analyzing
Block #84,348,487
14 transactions · 12 stateful · 2026-06-28 23:35:28 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,348,487 · 14 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
6w07w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x3732c6c9…ded6
0x34b655…2a6f
2 touches
0 conflicts
0x4da120a6…9249
0x34b655…2a6f
2 touches
0 conflicts
0x6fb323ed…337d
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
0x34b655…2a6f
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
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity