← previous blocknext block →recent activity
Analyzing
Block #92,325,890
10 transactions · 9 stateful · 2026-08-01 22:49:56 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,325,890 · 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
2w04w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa60eabc0…9f8c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfa0aa0d5…93d2
0x34b655…2a6f
4 touches
1 conflict
0xfaa5c672…5681
0x34b655…2a6f
4 touches
1 conflict
0x7b6d2deb…dde0
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x1e63ce19…13c8
0x34b655…2a6f
2 touches
0 conflicts
0x21d22421…0b7a
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 0xa60eabc0f8…119f8c
Audit this contract →
← previous block·next block →recent activity