← previous blocknext block →recent activity
Analyzing
Block #92,769,823
22 transactions · 20 stateful · 2026-08-03 12:03:51 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,769,823 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w211w012w313w114w418w019w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06ab8d8…3589
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x67c3a695…c858
0x40c49f…2af0
4 touches
1 conflict
0x819e5b42…dd33
0x40c49f…2af0
4 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x190ab6a6…5132
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
3 conflicts on slot 0xf06ab8d81b…9b3589
Audit this contract →
← previous block·next block →recent activity