← previous blocknext block →recent activity
Analyzing
Block #84,352,664
23 transactions · 20 stateful · 2026-06-29 00:03:22 UTC
Parallelism
78/100
Blocked
55%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,352,664 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w07w18w210w011w012w113w214w315w216w420w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xa9db7b4d…2957
0x40c49f…2af0
6 touches
3 conflicts
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x753da1ce…6bbd
0x34b655…2a6f
4 touches
1 conflict
0xb48409ab…ba0e
0x34b655…2a6f
4 touches
1 conflict
0xbb3504d4…b05f
0x34b655…2a6f
4 touches
1 conflict
0xcffc17bc…3544
0x34b655…2a6f
4 touches
1 conflict
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