← previous blocknext block →recent activity
Analyzing
Block #92,262,905
17 transactions · 17 stateful · 2026-08-01 17:33:10 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,262,905 · 17 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
1w02w13w04w06w17w210w314w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x06f96f59…f027
0x34b655…2a6f
6 touches
3 conflicts
0x16b73851…e01d
0x34b655…2a6f
6 touches
3 conflicts
0x242fd968…26ed
0x34b655…2a6f
6 touches
3 conflicts
0x36da12cd…371e
0x34b655…2a6f
6 touches
3 conflicts
0x42609666…d4f6
0x34b655…2a6f
6 touches
3 conflicts
0x4c0627bd…f5c3
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity