← previous blocknext block →recent activity
Analyzing
Block #92,442,433
18 transactions · 17 stateful · 2026-08-02 08:36:00 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,442,433 · 18 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
2w03w14w27w38w49w510w311w615w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0xbb7d7b7b…01cd
0x34b655…2a6f
10 touches
10 conflicts
0x35b89cd8…5092
0x34b655…2a6f
8 touches
6 conflicts
0xb83387da…d672
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xbb7cf334…a543
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity