← previous blocknext block →recent activity
Analyzing
Block #95,087,051
20 transactions · 18 stateful · 2026-08-11 14:37:40 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,087,051 · 20 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
1w02w15w06w17w08w19w210w317w018w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0x32e2bb09…8b3a
0x34b655…2a6f
4 touches
1 conflict
0x50afedcd…91cc
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity