pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,732,206
← previous block
next block →
recent activity
Analyzing
Block #98,732,206
19 transactions · 16 stateful · 2026-08-24 10:19:01 UTC
Parallelism
89
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,732,206
· 19 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
supply
#2
0x41a8f47c
#3
0xab083028
· blocks 1
#4
0x6ad2e98b
#5
execOrders
#6
0x59558d29
#7
execute
#8
execFwdPositionOpsV2
· blocks 1
#9
execFwdPositionOpsV2
#12
0x3f5c179b
#13
0x0c7abd22
#14
0x94defb17
#15
transfer
#16
0x6a8c1b0d
#17
setData
#18
execOrders
#10
execFwdPositionOpsV2
#11
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w0
10
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb55f6c75…c2d2
0xa6afd3…d132
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x9d929e0c…9421
0xa6afd3…d132
4 touches
1 conflict
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
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-WETH/USDC
1 conflict on slot
0xb55f6c750b…f2c2d2
Audit this contract →
← previous block
·
next block →
recent activity