← previous blocknext block →recent activity
Analyzing
Block #95,162,230
21 transactions · 20 stateful · 2026-08-11 20:55:50 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,162,230 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w09w114w015w316w417w518w319w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424934c8…f2f1
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0x6c3b70b7…b9a5
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
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
15 conflicts on slot 0x424934c865…4af2f1
Audit this contract →
← previous block·next block →recent activity