← previous blocknext block →recent activity
Analyzing
Block #95,404,815
20 transactions · 19 stateful · 2026-08-12 17:29:01 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,404,815 · 20 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
2w03w14w05w06w17w210w114w115w217w319w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd1f9150…430f
0x34b655…2a6f
8 touches
6 conflicts
0xe2d0ed2b…e416
0x34b655…2a6f
6 touches
3 conflicts
0x466c9e6a…e9de
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
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
6 conflicts on slot 0xcd1f91506d…e8430f
Audit this contract →
← previous block·next block →recent activity