← previous blocknext block →recent activity
Analyzing
Block #95,717,585
18 transactions · 16 stateful · 2026-08-13 19:43:48 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,717,585 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w38w49w411w513w116w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x9a9383a9…6bc7
0x34b655…2a6f
4 touches
1 conflict
0x9e5adfc8…489d
0x34b655…2a6f
4 touches
1 conflict
0xa13535db…1162
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 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity