← previous blocknext block →recent activity
Analyzing
Block #92,212,238
15 transactions · 14 stateful · 2026-08-01 13:18:20 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,212,238 · 15 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
5w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb3a63da…0a6c
0x34b655…2a6f
6 touches
3 conflicts
0xf2efbe2c…8732
0x34b655…2a6f
4 touches
1 conflict
0x7015836e…7341
0x34b655…2a6f
4 touches
1 conflict
0x8824d58e…fc00
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xe4c1abbf…26e3
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 0xdb3a63da5f…0a0a6c
Audit this contract →
← previous block·next block →recent activity