← previous blocknext block →recent activity
Analyzing
Block #92,586,604
23 transactions · 19 stateful · 2026-08-02 20:41:08 UTC
Parallelism
87/100
Blocked
47%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,586,604 · 23 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
2w03w14w05w06w17w08w19w211w113w115w216w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x19439a65…eb51
0x34b655…2a6f
4 touches
1 conflict
0x42d5e8f3…5930
0x34b655…2a6f
4 touches
1 conflict
0x6651d31f…eff6
0x34b655…2a6f
4 touches
1 conflict
0x7d07e5f7…6703
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity