pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,501,057
← previous block
next block →
recent activity
Analyzing
Block #108,501,057
11 transactions · 10 stateful · 2026-09-27 15:28:37 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,501,057
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x50a0b275
#2
exactOutputSingle
#3
0x0c7abd22
· blocks 1
#6
updatePrices
· blocks 1
#8
0x62be7533
#9
updatePriceFeedsIfNecessary
#10
execOrders
#4
0x0c7abd22
· blocks 1
#7
updatePrices
#5
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0x5d155ad9…708c
0xd32edf…ff58
3 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
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:
ShMonad (shMON)
1 conflict on slot
0xd9f18d9a4a…7f141d
Audit this contract →
← previous block
·
next block →
recent activity