← previous blocknext block →recent activity
Analyzing
Block #91,763,569
12 transactions · 12 stateful · 2026-07-30 23:41:30 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,763,569 · 12 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
1w02w13w24w05w16w17w28w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb30a641…a0e9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xe2e52e46…0894
0x34b655…2a6f
6 touches
3 conflicts
0xb566cc65…214d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3f5831e5…02b2
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 0xdb30a641b2…aca0e9
Audit this contract →
← previous block·next block →recent activity