← previous blocknext block →recent activity
Analyzing
Block #91,571,509
20 transactions · 18 stateful · 2026-07-30 07:35:22 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,571,509 · 20 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
1w02w13w24w15w06w27w310w011w112w113w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x5180f24b…0b96
0xd10cf1…7777
6 touches
3 conflicts
0x00000000…0000
0xd57e82…8ed4
6 touches
3 conflicts
0x00000000…0001
0xd57e82…8ed4
6 touches
3 conflicts
0x00000000…0003
0xd57e82…8ed4
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x6ac11407…0bcc
0x3bd359…433a
6 touches
3 conflicts
0xbc14748a…8cb1
0xd32edf…ff58
5 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
3 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity