← previous blocknext block →recent activity
Analyzing
Block #92,211,238
18 transactions · 17 stateful · 2026-08-01 13:13:18 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,211,238 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w210w011w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6a1f3a2…0b36
0x34b655…2a6f
6 touches
3 conflicts
0x167ca698…e836
0x34b655…2a6f
6 touches
3 conflicts
0x807bf45f…5016
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb25fa8e2…c9ef
0x34b655…2a6f
4 touches
1 conflict
0xc6352168…e091
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
3 conflicts on slot 0xf6a1f3a21b…c40b36
Audit this contract →
← previous block·next block →recent activity