← previous blocknext block →recent activity
Analyzing
Block #95,721,373
20 transactions · 18 stateful · 2026-08-13 20:02:51 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,721,373 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w27w38w411w312w416w517w619w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9d320e3…e03c
0x34b655…2a6f
10 touches
10 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0x8679531a…23cf
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
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 0xd9d320e3f6…20e03c
Audit this contract →
← previous block·next block →recent activity