← previous blocknext block →recent activity
Analyzing
Block #92,345,183
13 transactions · 11 stateful · 2026-08-02 00:26:57 UTC
Parallelism
46/100
Blocked
55%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,345,183 · 13 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
1w02w03w15w28w39w410w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90d75b1f…1664
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x21605a79…d719
0x34b655…2a6f
8 touches
6 conflicts
0xfb887a94…c508
0x34b655…2a6f
6 touches
3 conflicts
0x74eeff73…4115
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x50db8f2a…81d5
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
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
6 conflicts on slot 0x90d75b1f3e…4c1664
Audit this contract →
← previous block·next block →recent activity