← previous blocknext block →recent activity
Analyzing
Block #95,636,523
25 transactions · 21 stateful · 2026-08-13 12:55:01 UTC
Parallelism
68/100
Blocked
62%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,636,523 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w25w36w47w58w39w410w511w612w217w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
8 touches
6 conflicts
0xa7a84000…dd34
0x34b655…2a6f
6 touches
3 conflicts
0x85b86efd…d971
0x34b655…2a6f
5 touches
3 conflicts
0xab1d6786…884e
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity