pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,453,318
← previous block
next block →
recent activity
Analyzing
Block #106,453,318
12 transactions · 11 stateful · 2026-09-20 11:38:34 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,453,318
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
updatePrices
· blocks 1
#5
0x6aafc5be
#6
setData
#7
execFwdPositionOpsV2
#8
execOrders
· blocks 1
#10
0x6aafc5be
#11
execOrders
#4
updatePrices
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0xce119a07…0d1a
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x02fa927d…6468
0x34b655…2a6f
2 touches
0 conflicts
0x301e1c77…9e30
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
0xa5811d93b4…4d8c73
Audit this contract →
← previous block
·
next block →
recent activity