← previous blocknext block →recent activity
Analyzing
Block #95,405,155
39 transactions · 35 stateful · 2026-08-12 17:30:44 UTC
Parallelism
59/100
Blocked
66%
Avg conflicts / tx
1.67
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #95,405,155 · 39 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w06w17w28w19w210w311w412w516w617w718w826w133w1134w1237w1438w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc85f42b6…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa28d3a14…04bb
0x34b655…2a6f
8 touches
6 conflicts
0xe9452241…95a3
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
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 0xc85f42b605…b36f23
Audit this contract →
← previous block·next block →recent activity