← previous blocknext block →recent activity
Analyzing
Block #92,059,964
14 transactions · 13 stateful · 2026-08-01 00:32:30 UTC
Parallelism
50/100
Blocked
62%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,059,964 · 14 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
1w02w13w26w18w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0x1eb410fd…591d
0x34b655…2a6f
6 touches
3 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
6 touches
3 conflicts
0xfab1627b…b819
0x34b655…2a6f
6 touches
3 conflicts
0x167ca698…e836
0x34b655…2a6f
6 touches
3 conflicts
0x35184be6…0cf6
0xd32edf…ff58
5 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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity