← previous blocknext block →recent activity
Analyzing
Block #84,350,307
12 transactions · 11 stateful · 2026-06-28 23:47:37 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,350,307 · 12 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
1w05w06w17w28w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x5d11c8f8…31cc
0x40c49f…2af0
4 touches
1 conflict
0xf8a0cebb…b351
0x40c49f…2af0
3 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x06918491…394d
0x34b655…2a6f
2 touches
0 conflicts
0x0b56d384…2178
0x34b655…2a6f
2 touches
0 conflicts
0x24758f21…25bb
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity