← previous blocknext block →recent activity
Analyzing
Block #92,549,633
7 transactions · 6 stateful · 2026-08-02 17:35:10 UTC
Parallelism
43/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,549,633 · 7 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
2w03w14w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x6f4e7625…aba5
0x34b655…2a6f
4 touches
1 conflict
0x803eb45d…00bd
0x34b655…2a6f
4 touches
1 conflict
0xbcab7dbe…2825
0x34b655…2a6f
4 touches
1 conflict
0xd1603130…9680
0x34b655…2a6f
4 touches
1 conflict
0xe1bd732e…3304
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity