← previous blocknext block →recent activity
Analyzing
Block #95,654,270
21 transactions · 18 stateful · 2026-08-13 14:24:17 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,654,270 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w410w211w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81a169fb…d227
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0xc10b903d…2f54
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5e6a725f…3b35
0x34b655…2a6f
6 touches
3 conflicts
0x48a0f121…953b
0x34b655…2a6f
4 touches
1 conflict
0x490f1ae9…a441
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 0x81a169fb15…f9d227
Audit this contract →
← previous block·next block →recent activity