← previous blocknext block →recent activity
Analyzing
Block #92,013,619
15 transactions · 14 stateful · 2026-07-31 20:39:24 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,013,619 · 15 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
6w08w19w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004b
0x80c745…7210
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
10 touches
10 conflicts
0x213a54fa…c85f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5ef9751…101f
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x1ea2c53b…887a
0x754704…b603
2 touches
0 conflicts
0x2edbccf6…cc14
0x754704…b603
2 touches
0 conflicts
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: 0x80c74517…647210
10 conflicts on slot 0x0000000000…00004b
Audit this contract →
← previous block·next block →recent activity