← previous blocknext block →recent activity
Analyzing
Block #92,636,290
30 transactions · 26 stateful · 2026-08-03 00:51:01 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,636,290 · 30 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
1w05w06w17w08w19w210w315w317w018w119w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00a4f539…8b4a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb2fa1675…4e07
0x34b655…2a6f
6 touches
3 conflicts
0xcac6d3e1…66ca
0x34b655…2a6f
6 touches
3 conflicts
0x9a8482cc…8bee
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0x00a4f53997…138b4a
Audit this contract →
← previous block·next block →recent activity