pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,203,138
← previous block
next block →
recent activity
Analyzing
Block #92,203,138
8 transactions · 7 stateful · 2026-08-01 12:32:34 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,203,138
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 2
#4
0x39435dac
#6
0x6a6de7da
#7
setData
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x7eb2dbb4…e991
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x00075ae5…3a98
0x34b655…2a6f
4 touches
1 conflict
0x8d7e3f62…e2cc
0x34b655…2a6f
4 touches
1 conflict
0x8d7e3f62…e2cd
0x34b655…2a6f
4 touches
1 conflict
0x1a843f41…02aa
0x34b655…2a6f
2 touches
0 conflicts
0x3b689fd2…629c
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
3 conflicts on slot
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity