← previous blocknext block →recent activity
Analyzing
Block #92,404,310
14 transactions · 14 stateful · 2026-08-02 05:24:18 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,404,310 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w49w512w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
10 touches
10 conflicts
0x9cf9008a…d826
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xcb674fb5…9393
0x34b655…2a6f
8 touches
6 conflicts
0xb5838943…813d
0x34b655…2a6f
7 touches
6 conflicts
0x8f203394…f2db
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
15 conflicts on slot 0xd66696e0dc…230842
Audit this contract →
← previous block·next block →recent activity