← previous blocknext block →recent activity
Analyzing
Block #95,215,640
16 transactions · 16 stateful · 2026-08-12 01:24:28 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,215,640 · 16 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
1w02w04w05w16w27w38w414w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x5131a51b…548d
0x40c49f…2af0
9 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x50afedcd…91cc
0x34b655…2a6f
6 touches
3 conflicts
0x57b02276…db3f
0x34b655…2a6f
6 touches
3 conflicts
0x0140fbd3…d957
0x34b655…2a6f
4 touches
1 conflict
0xb514ce62…3397
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 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity