← previous blocknext block →recent activity
Analyzing
Block #95,782,432
23 transactions · 22 stateful · 2026-08-14 01:09:56 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,782,432 · 23 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
2w03w04w16w17w210w211w312w414w017w419w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
10 touches
10 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
8 touches
6 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc139c876…fe04
0x34b655…2a6f
6 touches
3 conflicts
0xc2726c34…a4c0
0x34b655…2a6f
6 touches
3 conflicts
0x935e0525…f741
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
10 conflicts on slot 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity