pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,111,090
← previous block
next block →
recent activity
Analyzing
Block #99,111,090
14 transactions · 13 stateful · 2026-08-25 18:12:10 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,111,090
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
0x6ad2e98b
#3
0xab083028
#4
0x5acec890
· blocks 1
#6
0x59558d29
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
0x3f5c179b
#10
forward
#11
claim
#12
0xed82b078
#13
setData
#5
0x928e4afa
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0d59ed6c…8f3c
0x34b655…2a6f
2 touches
0 conflicts
0x32287d4a…6699
0x34b655…2a6f
2 touches
0 conflicts
0x676207a8…5d7e
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
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:
Perpl
1 conflict on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity