← previous blocknext block →recent activity
Analyzing
Block #91,267,127
21 transactions · 19 stateful · 2026-07-29 06:01:53 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,267,127 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w17w18w29w313w414w516w218w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94de4d05…ad01
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x7a73cd91…d31f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x339e553b…ba52
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
15 conflicts on slot 0x94de4d05c1…d4ad01
Audit this contract →
← previous block·next block →recent activity