← previous blocknext block →recent activity
Analyzing
Block #92,485,680
22 transactions · 21 stateful · 2026-08-02 12:13:34 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,485,680 · 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
1w03w04w15w27w38w09w110w211w312w413w514w617w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xaeceab68…352c
0x34b655…2a6f
9 touches
10 conflicts
0xdcd1a070…7e92
0x34b655…2a6f
7 touches
6 conflicts
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
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
21 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity