← previous blocknext block →recent activity
Analyzing
Block #92,243,895
16 transactions · 16 stateful · 2026-08-01 15:57:32 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,243,895 · 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
1w02w03w14w15w07w28w39w410w511w612w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbc684438…8bc3
0x34b655…2a6f
10 touches
10 conflicts
0xa5a8ffca…8de2
0x34b655…2a6f
8 touches
6 conflicts
0x3270d9f8…099a
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
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
21 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity