← previous blocknext block →recent activity
Analyzing
Block #84,364,325
25 transactions · 20 stateful · 2026-06-29 01:21:09 UTC
Parallelism
88/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,364,325 · 25 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
1w02w04w05w18w29w011w012w113w114w015w216w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3572c95…9c4a
0x2a68ba…90c5
6 touches
3 conflicts
0x975680c7…0e39
0xa6afd3…d132
6 touches
3 conflicts
0x0ee4fe41…9382
0x34b655…2a6f
4 touches
1 conflict
0x2b1b66e9…d1c4
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0x7b6d2deb…dde0
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
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 0xb3572c958a…0d9c4a
Audit this contract →
← previous block·next block →recent activity