← previous blocknext block →recent activity
Analyzing
Block #92,600,839
17 transactions · 17 stateful · 2026-08-02 21:52:44 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,600,839 · 17 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
1w02w14w25w36w47w510w312w413w514w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32ffd4e4…5fdd
0x34b655…2a6f
8 touches
6 conflicts
0xa5f0a59c…0ab2
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x11cecbd3…9d6c
0x34b655…2a6f
6 touches
3 conflicts
0x3dae5ee1…721b
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x4bb0bfb0…8f11
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 0x32ffd4e4c5…d05fdd
Audit this contract →
← previous block·next block →recent activity