← previous blocknext block →recent activity
Analyzing
Block #92,864,402
19 transactions · 17 stateful · 2026-08-03 19:59:52 UTC
Parallelism
63/100
Blocked
41%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,864,402 · 19 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
1w05w06w17w210w111w312w413w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc683bfb0…3bbc
0x34b655…2a6f
10 touches
10 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
10 touches
10 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x3b9bb58c…e73a
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity