← previous blocknext block →recent activity
Analyzing
Block #95,181,400
13 transactions · 12 stateful · 2026-08-11 22:32:15 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,181,400 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x320b9f7c…3fec
0x34b655…2a6f
6 touches
3 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
6 touches
3 conflicts
0x785c87ba…a0f1
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x9a8af3c2…e4ae
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 0x320b9f7cf3…e83fec
Audit this contract →
← previous block·next block →recent activity