← previous blocknext block →recent activity
Analyzing
Block #95,579,614
14 transactions · 13 stateful · 2026-08-13 08:08:46 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,579,614 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c912a68…3b21
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x35c68080…aace
0x851145…3f07
4 touches
1 conflict
0xc9327614…ba36
0x851145…3f07
4 touches
1 conflict
0xd6265424…0d3a
0x851145…3f07
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
1 conflict on slot 0x1c912a689a…d53b21
Audit this contract →
← previous block·next block →recent activity