← previous blocknext block →recent activity
Analyzing
Block #92,434,459
13 transactions · 12 stateful · 2026-08-02 07:55:54 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,434,459 · 13 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
1w03w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6ff8a7f4…932e
0x065c9d…c394
4 touches
1 conflict
0x8664c626…59d8
0x065c9d…c394
3 touches
1 conflict
0x92ca529b…e8e8
0x065c9d…c394
3 touches
1 conflict
0x12fb0693…c249
0x34b655…2a6f
2 touches
0 conflicts
0x1f620d34…475c
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity