← previous blocknext block →recent activity
Analyzing
Block #92,968,613
18 transactions · 16 stateful · 2026-08-04 04:44:08 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
0.89
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,968,613 · 18 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
1w04w15w06w07w18w29w310w211w113w314w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x216ffe66…1f94
0x34b655…2a6f
8 touches
6 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
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
6 conflicts on slot 0x216ffe6648…bf1f94
Audit this contract →
← previous block·next block →recent activity