pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,789,201
← previous block
next block →
recent activity
Analyzing
Block #92,789,201
11 transactions · 10 stateful · 2026-08-03 13:41:22 UTC
Parallelism
64
/100
Blocked
30
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,789,201
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 3
#6
execFwdPositionOps
#7
executeBatch
#8
0x3f5c179b
#9
withdrawReserve
#10
setData
#3
0x5acec890
· blocks 2
#4
0x5acec890
· blocks 1
#5
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x11ff9a2b…1dd7
0x34b655…2a6f
2 touches
0 conflicts
0x1ad59947…dd02
0x34b655…2a6f
2 touches
0 conflicts
0x3118505b…795e
0x34b655…2a6f
2 touches
0 conflicts
0x410b84ab…1dbc
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
6 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity