← previous blocknext block →recent activity
Analyzing
Block #84,606,082
10 transactions · 8 stateful · 2026-06-30 04:13:28 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,606,082 · 10 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
4w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1ecf8801…b220
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5239bcf9…a5a6
0x065c9d…c394
2 touches
0 conflicts
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0xa24d5eb9…0d83
0x065c9d…c394
2 touches
0 conflicts
0x06c8b5a5…48b1
0x34b655…2a6f
2 touches
0 conflicts
0x2666137c…e4ea
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