← previous blocknext block →recent activity
Analyzing
Block #95,387,035
47 transactions · 43 stateful · 2026-08-12 15:59:03 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
2.7
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #95,387,035 · 47 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w08w19w210w315w617w118w220w722w929w1030w1032w133w1134w236w1238w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
18 touches
36 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xc85f42b6…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xf2b36ab5…39d8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity