← previous blocknext block →recent activity
Analyzing
Block #95,371,715
10 transactions · 9 stateful · 2026-08-12 14:41:28 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,371,715 · 10 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
1w02w13w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71cc73a0…d523
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x12e8fcf0…63bb
0x34b655…2a6f
2 touches
0 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
2 touches
0 conflicts
0x25957369…c648
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 0x71cc73a039…60d523
Audit this contract →
← previous block·next block →recent activity