← previous blocknext block →recent activity
Analyzing
Block #92,274,415
16 transactions · 15 stateful · 2026-08-01 18:31:03 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,274,415 · 16 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
1w02w13w24w35w38w412w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b257415…b10f
0x34b655…2a6f
10 touches
10 conflicts
0x940ef645…018e
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xeca6a5e8…808c
0x34b655…2a6f
4 touches
1 conflict
0x9a6bc012…7495
0x34b655…2a6f
4 touches
1 conflict
0xb8482bdb…9c6e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
10 conflicts on slot 0x2b257415f5…44b10f
Audit this contract →
← previous block·next block →recent activity