← previous blocknext block →recent activity
Analyzing
Block #95,586,611
16 transactions · 15 stateful · 2026-08-13 08:43:57 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,586,611 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w09w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
8 touches
6 conflicts
0xff28ee17…414e
0x34b655…2a6f
4 touches
1 conflict
0x835ff4a1…e866
0x34b655…2a6f
4 touches
1 conflict
0x8665471d…2214
0x34b655…2a6f
4 touches
1 conflict
0xa56083c4…607c
0x34b655…2a6f
4 touches
1 conflict
0xb4581f8f…3fa4
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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: Perpl
6 conflicts on slot 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity