pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,434,711
← previous block
next block →
recent activity
Analyzing
Block #106,434,711
10 transactions · 9 stateful · 2026-09-20 10:04:52 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,434,711
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
· blocks 1
#4
0x59558d29
#5
setData
#6
forward
#7
0x6aafafc7
#8
execOrders
· blocks 1
#3
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…000b
0x23c377…ea93
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x1d1eb3d2…d573
0x34b655…2a6f
2 touches
0 conflicts
0x4cf825c3…0e8d
0x34b655…2a6f
2 touches
0 conflicts
0x536bb020…37a5
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity