← previous blocknext block →recent activity
Analyzing
Block #95,425,285
17 transactions · 15 stateful · 2026-08-12 19:12:31 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,425,285 · 17 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
1w03w04w15w26w37w48w310w111w413w014w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c8753e8…d214
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x73f2022f…8ba2
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0xc782ec05…5bb2
0xa6afd3…d132
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0dd3d3cd…7281
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
3 conflicts on slot 0x1c8753e8cf…47d214
Audit this contract →
← previous block·next block →recent activity