← previous blocknext block →recent activity
Analyzing
Block #92,760,181
21 transactions · 21 stateful · 2026-08-03 11:15:19 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,760,181 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w17w18w29w310w411w512w618w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x2101bec4…84b9
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x743061ce…a4ac
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
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
10 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity