← previous blocknext block →recent activity
Analyzing
Block #92,822,645
10 transactions · 8 stateful · 2026-08-03 16:29:36 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,822,645 · 10 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
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f46ea6…18c4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0e4000ee…afb9
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
2 touches
0 conflicts
0x253bf197…1e1a
0x34b655…2a6f
2 touches
0 conflicts
0x351d96b9…c5df
0x34b655…2a6f
2 touches
0 conflicts
0x36a6e1a0…4d87
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 0x63f46ea6ba…5318c4
Audit this contract →
← previous block·next block →recent activity