← previous blocknext block →recent activity
Analyzing
Block #92,569,287
23 transactions · 20 stateful · 2026-08-02 19:14:01 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,569,287 · 23 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
2w03w17w08w29w310w412w515w617w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x620b761c…270e
0x34b655…2a6f
12 touches
15 conflicts
0xba29d2f2…cd5b
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0x4e135144…4167
0x34b655…2a6f
8 touches
6 conflicts
0x6719a767…9d62
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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