← previous blocknext block →recent activity
Analyzing
Block #92,060,465
50 transactions · 45 stateful · 2026-08-01 00:35:01 UTC
Parallelism
90/100
Blocked
9%
Avg conflicts / tx
0.2
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,060,465 · 50 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w345w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbffde283…3385
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x5827be1e…2a9f
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
3 touches
1 conflict
0x922cbc0c…51aa
0x34b655…2a6f
3 touches
1 conflict
0x47d0b145…17b9
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity