pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,848,244
← previous block
next block →
recent activity
Analyzing
Block #107,848,244
13 transactions · 13 stateful · 2026-09-25 08:43:02 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,848,244
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9ac0761c
#2
0x9ac0761c
#3
0x9ac0761c
#4
matchOrders
#5
0xab083028
#6
0x0c7abd22
· blocks 1
#8
0x5acec890
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
setData
#12
execOrders
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb87
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xa6a606d2…4e9d
0xd32edf…ff58
3 touches
1 conflict
0x46279ae7…20dd
0x34ae4d…3fc5
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x1ddcfe3f…9a06
0x754704…b603
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
0x0000000000…000012
Audit this contract →
← previous block
·
next block →
recent activity