← previous blocknext block →recent activity
Analyzing
Block #95,300,209
13 transactions · 11 stateful · 2026-08-12 08:39:12 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,300,209 · 13 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
1w02w13w24w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xb30b036e…c0af
0x34b655…2a6f
4 touches
1 conflict
0xe8497ba6…da0e
0x34b655…2a6f
4 touches
1 conflict
0xb6dd5be0…26d6
0x34b655…2a6f
4 touches
1 conflict
0xc6fabe47…654e
0x34b655…2a6f
4 touches
1 conflict
0x856d2776…04c9
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
3 conflicts on slot 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity