← previous blocknext block →recent activity
Analyzing
Block #92,969,535
25 transactions · 18 stateful · 2026-08-04 04:48:46 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,969,535 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w19w011w113w214w115w118w220w222w023w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x7701846c…9b82
0x851145…3f07
6 touches
3 conflicts
0x80a745fc…ce9e
0x851145…3f07
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x9ea0c7a7…f14e
0x34b655…2a6f
4 touches
1 conflict
0xa558e115…fc88
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity