pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,879,805
← previous block
next block →
recent activity
Analyzing
Block #100,879,805
14 transactions · 11 stateful · 2026-08-31 22:51:36 UTC
Parallelism
86
/100
Blocked
18
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,879,805
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xab083028
· blocks 1
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#8
placeBet
#9
forward
#10
0x6a9605f0
#11
setData
#12
0xb49548…09d3
#13
execOrders
#3
0xab083028
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61fee84f…1fbc
0x065c9d…c394
4 touches
1 conflict
0x48ed1159…abe9
0x34ae4d…3fc5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x61fee84f5c…b91fbc
Audit this contract →
← previous block
·
next block →
recent activity