← previous blocknext block →recent activity
Analyzing
Block #84,064,995
14 transactions · 12 stateful · 2026-06-27 16:07:05 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,064,995 · 14 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
1w02w07w18w19w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x117f1699…b264
0xa6afd3…d132
4 touches
1 conflict
0x763dd151…d9de
0xa6afd3…d132
4 touches
1 conflict
0x09a4820b…2db8
0x34b655…2a6f
4 touches
1 conflict
0x0fa34c35…499f
0xa6afd3…d132
3 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0cdf9369…5331
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