← previous blocknext block →recent activity
Analyzing
Block #95,722,474
10 transactions · 8 stateful · 2026-08-13 20:08:23 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,722,474 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf2b36ab5…39d8
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
2 touches
0 conflicts
0x43b34fb2…7b88
0x34b655…2a6f
2 touches
0 conflicts
0x63759c44…7f20
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity