← previous blocknext block →recent activity
Analyzing
Block #92,357,403
9 transactions · 9 stateful · 2026-08-02 01:28:25 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,357,403 · 9 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
1w02w14w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5827be1e…2a9f
0x34b655…2a6f
4 touches
1 conflict
0x8aba0984…9fa0
0xd32edf…ff58
3 touches
1 conflict
0x35a9f06c…7689
0x34b655…2a6f
2 touches
0 conflicts
0x4275e5c5…2356
0x34b655…2a6f
2 touches
0 conflicts
0x67708716…f9b6
0x34b655…2a6f
2 touches
0 conflicts
0x6d1b72ee…6b78
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity