← previous blocknext block →recent activity
Analyzing
Block #92,442,802
16 transactions · 15 stateful · 2026-08-02 08:37:51 UTC
Parallelism
56/100
Blocked
47%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,442,802 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w17w28w311w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
8 touches
6 conflicts
0x0db8e93a…7dd1
0x34b655…2a6f
6 touches
3 conflicts
0x59a07ac0…728d
0x34b655…2a6f
6 touches
3 conflicts
0x7e1faa73…bfbf
0x34b655…2a6f
6 touches
3 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
6 touches
3 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 0x7aad02c682…feb979
Audit this contract →
← previous block·next block →recent activity