pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,301,082
← previous block
next block →
recent activity
Analyzing
Block #106,301,082
12 transactions · 12 stateful · 2026-09-19 22:52:22 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,301,082
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0x5acec890
· blocks 1
#4
0x5acec890
#6
0x5acec890
#7
0x59558d29
#8
executeRelayerRefundLeaf
#9
setData
#10
0x57368ddf
#5
0x928e4afa
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdddf97e5…1c90
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x6158910e…f7f3
0x34b655…2a6f
2 touches
0 conflicts
0x65903ef9…2567
0x34b655…2a6f
2 touches
0 conflicts
0x75f928fc…0465
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
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
0xdddf97e500…0f1c90
Audit this contract →
← previous block
·
next block →
recent activity