← previous blocknext block →recent activity
Analyzing
Block #92,056,589
38 transactions · 34 stateful · 2026-08-01 00:15:32 UTC
Parallelism
79/100
Blocked
65%
Avg conflicts / tx
1.34
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,056,589 · 38 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w47w58w69w610w012w715w517w018w119w230w335w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x15a7c2ea…5855
0xd32edf…ff58
9 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0002
0x91855e…ac7e
8 touches
6 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity