← previous blocknext block →recent activity
Analyzing
Block #92,299,505
14 transactions · 12 stateful · 2026-08-01 20:37:15 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,299,505 · 14 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
1w06w17w29w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708f4f51…40e8
0x34b655…2a6f
8 touches
6 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x3e3b859f…3654
0x34b655…2a6f
4 touches
1 conflict
0xd08098a8…f0a6
0x34b655…2a6f
4 touches
1 conflict
0x68caa37b…c795
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 0x708f4f5118…5440e8
Audit this contract →
← previous block·next block →recent activity