pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,157,738
← previous block
next block →
recent activity
Analyzing
Block #91,157,738
10 transactions · 10 stateful · 2026-07-28 20:51:29 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,157,738
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
· blocks 1
#3
0x0f6795d9
#4
0x0f6795d9
· blocks 1
#5
0x3f5c179b
#7
0x6a6916c9
#8
setData
#6
0x0f6795d9
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x9fbc6a76…9c29
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x21d22421…0b7a
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x3e2663d3…a620
0x34b655…2a6f
2 touches
0 conflicts
0x45d2c10e…7f81
0x34b655…2a6f
2 touches
0 conflicts
0x5babb0df…9cf9
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity