← previous blocknext block →recent activity
Analyzing
Block #95,005,796
22 transactions · 21 stateful · 2026-08-11 07:48:07 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
0.91
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,005,796 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w07w18w09w113w114w215w217w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc70dd80f…d075
0x34b655…2a6f
8 touches
6 conflicts
0x81a9d526…20e6
0xd32edf…ff58
7 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x87e68d66…4ab4
0x065c9d…c394
5 touches
3 conflicts
0x3a62fa13…21ee
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4a15396b…a00f
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
6 conflicts on slot 0xc70dd80f5d…82d075
Audit this contract →
← previous block·next block →recent activity