← previous blocknext block →recent activity
Analyzing
Block #95,124,296
54 transactions · 46 stateful · 2026-08-11 17:45:02 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
2.57
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #95,124,296 · 54 txs across 20 waves · depth 20
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
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w19w110w011w112w213w314w420w325w626w736w1440w242w1643w344w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xacd1b162…bee6
0x34b655…2a6f
14 touches
21 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
10 touches
10 conflicts
0x7e1faa73…bfbf
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x2385516f…eca5
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity