← previous blocknext block →recent activity
Analyzing
Block #95,539,267
26 transactions · 22 stateful · 2026-08-13 04:45:51 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,539,267 · 26 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
1w02w13w24w38w012w015w116w217w318w419w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc106cfcd…b256
0x34b655…2a6f
8 touches
6 conflicts
0x00b16471…4ea4
0xd32edf…ff58
7 touches
6 conflicts
0x58ae9c0f…d6c8
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xa779293b…5e59
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0672e4a2…8d1f
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 0xc106cfcdd8…49b256
Audit this contract →
← previous block·next block →recent activity