← previous blocknext block →recent activity
Analyzing
Block #92,548,247
16 transactions · 14 stateful · 2026-08-02 17:28:12 UTC
Parallelism
63/100
Blocked
36%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,548,247 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w29w310w411w5
- 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
8 touches
6 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x2ccb18d1…a00c
0x34b655…2a6f
5 touches
3 conflicts
0x699ee60f…de01
0x34b655…2a6f
4 touches
1 conflict
0x76ee7653…6922
0x34b655…2a6f
4 touches
1 conflict
0xdba3b90b…02bd
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
10 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity