pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,531,136
← previous block
next block →
recent activity
Analyzing
Block #92,531,136
10 transactions · 10 stateful · 2026-08-02 16:02:10 UTC
Parallelism
60
/100
Blocked
40
%
Avg conflicts / tx
0.4
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,531,136
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x5acec890
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a6f6a79
#6
setData
#8
0x59558d29
· blocks 1
#2
0x5acec890
· blocks 1
#9
0x59558d29
#3
execFwdPositionOps
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w3
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92115abd…ad76
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x6e6b8ec7…2197
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x7f127ad0…2bd6
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
0x92115abda4…1fad76
Audit this contract →
← previous block
·
next block →
recent activity