← previous blocknext block →recent activity
Analyzing
Block #95,528,915
22 transactions · 19 stateful · 2026-08-13 03:53:46 UTC
Parallelism
64/100
Blocked
47%
Avg conflicts / tx
1.18
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,528,915 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w26w37w48w510w611w712w717w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0672e4a2…8d1f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x85167706…718e
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x351a25e6…4910
0x34b655…2a6f
6 touches
3 conflicts
0x83a3f833…8268
0x34b655…2a6f
4 touches
1 conflict
0x5cb1b98c…c3e3
0xa6afd3…d132
4 touches
1 conflict
0x8cd684d0…c3cb
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
15 conflicts on slot 0x0672e4a279…2f8d1f
Audit this contract →
← previous block·next block →recent activity