← previous blocknext block →recent activity
Analyzing
Block #95,750,661
15 transactions · 13 stateful · 2026-08-13 22:30:09 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,750,661 · 15 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
1w02w13w04w16w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68256d5a…db24
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xeb95de02…fdc1
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xb7998ba6…4cc3
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
1 conflict on slot 0x68256d5a69…43db24
Audit this contract →
← previous block·next block →recent activity