← previous blocknext block →recent activity
Analyzing
Block #92,243,289
21 transactions · 21 stateful · 2026-08-01 15:54:29 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,243,289 · 21 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
3w06w07w18w29w311w012w113w414w515w617w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6859525f…4f99
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
10 touches
10 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0xa5a8ffca…8de2
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 0x6859525f81…8b4f99
Audit this contract →
← previous block·next block →recent activity