← previous blocknext block →recent activity
Analyzing
Block #84,176,917
23 transactions · 19 stateful · 2026-06-28 04:32:20 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,176,917 · 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
1w03w012w113w214w315w416w017w119w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x5cc8dd43…8cf2
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x9ac79c76…c4a9
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
10 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity