← previous blocknext block →recent activity
Analyzing
Block #92,071,263
8 transactions · 8 stateful · 2026-08-01 01:29:21 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,071,263 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56d6548…50a4
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x7fa44fe8…484e
0x34b655…2a6f
4 touches
1 conflict
0x14eb2f47…8a2e
0x34b655…2a6f
4 touches
1 conflict
0x70a7b5d6…fe0e
0x34b655…2a6f
2 touches
0 conflicts
0xb96d00bc…8144
0x34b655…2a6f
2 touches
0 conflicts
0xba228f10…2593
0x34b655…2a6f
2 touches
0 conflicts
0xba228f10…2594
0x34b655…2a6f
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: Perpl
1 conflict on slot 0xc56d654866…5050a4
Audit this contract →
← previous block·next block →recent activity