pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,559,799
← previous block
next block →
recent activity
Analyzing
Block #92,559,799
11 transactions · 10 stateful · 2026-08-02 18:26:18 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,559,799
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
0x4d8dc985
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#7
redeemDelegations
#8
0x39435dac
#9
setData
#10
0x59558d29
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd58474a3…aff4
0x34b655…2a6f
4 touches
1 conflict
0xb2fa1675…4e07
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x6507044e…bcd6
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x4a2dd131…efef
0x34b655…2a6f
2 touches
0 conflicts
0x5bf917f9…f971
0x34b655…2a6f
2 touches
0 conflicts
0x5d782da3…0d95
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
0xd58474a3e4…6eaff4
Audit this contract →
← previous block
·
next block →
recent activity