← previous blocknext block →recent activity
Analyzing
Block #92,696,936
17 transactions · 16 stateful · 2026-08-03 05:56:58 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,696,936 · 17 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
1w04w07w18w29w310w011w112w214w015w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xbfd33a92…5c35
0x34b655…2a6f
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x019883…2a9a
6 touches
3 conflicts
0x00000000…0003
0x019883…2a9a
6 touches
3 conflicts
0x00000000…0002
0x019883…2a9a
6 touches
3 conflicts
0xa10c86f8…4b74
0x3bd359…433a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity