pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,684,590
← previous block
next block →
recent activity
Analyzing
Block #108,684,590
10 transactions · 10 stateful · 2026-09-28 06:52:55 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,684,590
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x59558d29
#3
0x5de3085d
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x0c7abd22
#7
0x3f5c179b
#8
execFwdPositionOpsV2
#9
setData
#4
0x7513bc49
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ac338e8…93bb
0x3bd359…433a
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x97199b…5aad
4 touches
1 conflict
0xe2cb724f…81ed
0xd8e004…7777
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0xb771853a…e31d
0xe1c8b7…3022
4 touches
1 conflict
0x09000000…0001
0x000000…1000
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:
Wrapped MON (WMON)
1 conflict on slot
0x6ac338e84d…0793bb
Audit this contract →
← previous block
·
next block →
recent activity