← previous blocknext block →recent activity
Analyzing
Block #95,381,509
11 transactions · 10 stateful · 2026-08-12 15:31:04 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,381,509 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7523c6af…ea66
0x34b655…2a6f
6 touches
3 conflicts
0x7a18d90e…9c1a
0x34b655…2a6f
6 touches
3 conflicts
0xca713a22…3083
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
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
3 conflicts on slot 0x7523c6affe…33ea66
Audit this contract →
← previous block·next block →recent activity