← previous blocknext block →recent activity
Analyzing
Block #95,548,687
12 transactions · 10 stateful · 2026-08-13 05:33:13 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,548,687 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c2f6464…6a7e
0x34b655…2a6f
4 touches
1 conflict
0xa241f0f0…ca94
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x041bddcd…d2cf
0x34b655…2a6f
2 touches
0 conflicts
0x087cdd55…0693
0x34b655…2a6f
2 touches
0 conflicts
0x0e246445…9e0e
0x34b655…2a6f
2 touches
0 conflicts
0x1e31292c…8b83
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x6c2f6464cf…cb6a7e
Audit this contract →
← previous block·next block →recent activity