pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,045,899
← previous block
next block →
recent activity
Analyzing
Block #106,045,899
13 transactions · 13 stateful · 2026-09-19 01:28:03 UTC
Parallelism
77
/100
Blocked
15
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,045,899
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
multicall
#2
0xab083028
#3
execOrders
· blocks 2
#6
0x59558d29
#7
updatePrices
#8
0x3f5c179b
#9
execFwdPositionOpsV2
#10
forward
#11
0x6aade527
#12
setData
#4
execOrders
· blocks 1
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0004
0x0898c3…f274
2 touches
0 conflicts
0x035f11ba…07e7
0x0898c3…f274
2 touches
0 conflicts
0x899a0e35…c279
0x0898c3…f274
2 touches
0 conflicts
0x892e4d22…3afa
0x0bb150…64ef
2 touches
0 conflicts
0x00000000…0008
0x5aff25…7440
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
3 conflicts on slot
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity