← previous blocknext block →recent activity
Analyzing
Block #92,869,755
15 transactions · 14 stateful · 2026-08-03 20:26:47 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,869,755 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb39cb1d8…effa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x3a07a361…ab39
0x34b655…2a6f
4 touches
1 conflict
0x3b9bb58c…e73a
0x34b655…2a6f
4 touches
1 conflict
0x58123a85…6f7d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c3
0x1b6862…e19c
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
3 conflicts on slot 0xb39cb1d8c6…28effa
Audit this contract →
← previous block·next block →recent activity