pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,104,828
← previous block
next block →
recent activity
Analyzing
Block #100,104,828
11 transactions · 11 stateful · 2026-08-29 05:48:05 UTC
Parallelism
73
/100
Blocked
36
%
Avg conflicts / tx
0.55
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,104,828
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#3
matchOrders
#4
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#9
bet
#2
0x0c7abd22
· blocks 1
#8
batchUpdate
· blocks 1
#5
0x0c7abd22
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
8
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbc6e634…e169
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x788d3bf0…3267
0xd32edf…ff58
5 touches
3 conflicts
0xcba76693…20ff
0xfa32f9…f3f0
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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)
3 conflicts on slot
0xdbc6e63468…c6e169
Audit this contract →
← previous block
·
next block →
recent activity