← previous blocknext block →recent activity
Analyzing
Block #95,152,843
23 transactions · 21 stateful · 2026-08-11 20:08:37 UTC
Parallelism
65/100
Blocked
52%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,152,843 · 23 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
1w02w13w24w15w36w47w511w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
10 touches
10 conflicts
0x734ee320…caae
0x34b655…2a6f
10 touches
10 conflicts
0xbe9baf16…df37
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xfb8facd9…d405
0x34b655…2a6f
6 touches
3 conflicts
0x17c3727d…cb0e
0x34b655…2a6f
6 touches
3 conflicts
0x2c429f11…0652
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity