← previous blocknext block →recent activity
Analyzing
Block #92,447,695
34 transactions · 24 stateful · 2026-08-02 09:02:27 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,447,695 · 34 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
1w08w010w112w013w117w119w020w121w224w230w331w032w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0xc44a1acb…af47
0x34b655…2a6f
5 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
5 touches
3 conflicts
0x8702a009…24b2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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
3 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity