← previous blocknext block →recent activity
Analyzing
Block #92,461,185
16 transactions · 14 stateful · 2026-08-02 10:10:18 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,461,185 · 16 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
1w03w04w17w29w310w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x4e50038e…6e29
0x34b655…2a6f
6 touches
3 conflicts
0x9ba69cff…749c
0x34b655…2a6f
6 touches
3 conflicts
0x7054365a…650d
0x34b655…2a6f
5 touches
3 conflicts
0xf394e6ad…f568
0x34b655…2a6f
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…00c9
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
6 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity