pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,445,908
← previous block
next block →
recent activity
Analyzing
Block #92,445,908
10 transactions · 7 stateful · 2026-08-02 08:53:28 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,445,908
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#6
updatePosition
#7
0x39435dac
#8
0x39435dac
#9
setData
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xcfe06a18…b5b5
0x2b46c0…1669
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
0xafb8e71eb0…ec9285
Audit this contract →
← previous block
·
next block →
recent activity