← previous blocknext block →recent activity
Analyzing
Block #92,770,788
22 transactions · 18 stateful · 2026-08-03 12:08:42 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.68
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,770,788 · 22 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
5w08w011w112w213w314w416w517w119w6
- 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
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0x30cb7412…207e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5cc477b5…1cf3
0x34b655…2a6f
6 touches
3 conflicts
0x68caa37b…c795
0x34b655…2a6f
6 touches
3 conflicts
0x7e901f57…30ff
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity