pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,494,493
← previous block
next block →
recent activity
Analyzing
Block #108,494,493
13 transactions · 10 stateful · 2026-09-27 14:55:34 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,494,493
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x9ac0761c
#2
0x9ac0761c
· blocks 1
#4
0x0c7abd22
#5
0x59558d29
#6
0x59558d29
#7
updatePrices
#8
0x5acec890
#9
execFwdPositionOpsV2
#10
setData
#11
setData
#12
execOrders
#3
0x9ac0761c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4aa8b305…4ace
0x860869…ff01
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0x174fbe56…acd2
0x34b655…2a6f
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:
0x8608690f…c8ff01
1 conflict on slot
0x4aa8b3059e…9d4ace
Audit this contract →
← previous block
·
next block →
recent activity