← previous blocknext block →recent activity
Analyzing
Block #84,619,291
12 transactions · 11 stateful · 2026-06-30 05:41:23 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,619,291 · 12 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
1w03w04w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xebcd072d…7736
0x5afd3e…7620
4 touches
1 conflict
0x4de67fca…e8a3
0x5afd3e…7620
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x81f46526…4c0d
0x5afd3e…7620
2 touches
0 conflicts
0x838e0f29…7f64
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x4039b31f…0f4a
0x754704…b603
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