← previous blocknext block →recent activity
Analyzing
Block #95,200,616
25 transactions · 23 stateful · 2026-08-12 00:08:54 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,200,616 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w19w010w111w112w213w315w416w517w618w719w220w221w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
14 touches
21 conflicts
0x2b54cadb…4425
0xd18b7e…414b
14 touches
21 conflicts
0x301de477…1b43
0x40c49f…2af0
13 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b32f984…c0a0
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0xa6464996…3af9
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
21 conflicts on slot 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity