← previous blocknext block →recent activity
Analyzing
Block #95,525,466
19 transactions · 18 stateful · 2026-08-13 03:36:25 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,525,466 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w49w410w512w113w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd684d0…c3cb
0x34b655…2a6f
10 touches
10 conflicts
0x87328177…9bfd
0x34b655…2a6f
8 touches
6 conflicts
0xb4405eb4…c857
0x34b655…2a6f
6 touches
3 conflicts
0xbcdc582f…a65d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5efd583e…c41a
0x34b655…2a6f
6 touches
3 conflicts
0x24521815…c677
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 0x8cd684d0d7…f5c3cb
Audit this contract →
← previous block·next block →recent activity