← previous blocknext block →recent activity
Analyzing
Block #92,049,703
14 transactions · 13 stateful · 2026-07-31 23:40:53 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,049,703 · 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
3w04w15w28w09w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9aa7ce75…e54e
0x7b9256…1fb2
4 touches
1 conflict
0x783f443b…45c3
0x7b9256…1fb2
4 touches
1 conflict
0x783f443b…45c4
0x7b9256…1fb2
4 touches
1 conflict
0x9aa7ce75…e54a
0x7b9256…1fb2
4 touches
1 conflict
0x9aa7ce75…e54b
0x7b9256…1fb2
4 touches
1 conflict
0x784eaad2…d176
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d177
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity