pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,122,424
← previous block
next block →
recent activity
Analyzing
Block #100,122,424
11 transactions · 10 stateful · 2026-08-29 07:16:43 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,122,424
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0xab083028
#4
0x59558d29
#5
0x59558d29
#6
execOrders
· blocks 1
#8
0x94defb17
· blocks 1
#9
forward
#7
execFwdPositionOpsV2
#10
bet
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb88ce18…68ca
0x8964d7…10f8
4 touches
1 conflict
0xdb88ce18…68cb
0x8964d7…10f8
4 touches
1 conflict
0xdb88ce18…68ce
0x8964d7…10f8
4 touches
1 conflict
0xdb88ce18…68cf
0x8964d7…10f8
4 touches
1 conflict
0xdb88ce18…68d1
0x8964d7…10f8
4 touches
1 conflict
0x1a3d2527…8ca0
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc284529b…9553
0x34b655…2a6f
4 touches
1 conflict
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:
0x8964d7c9…5b10f8
1 conflict on slot
0xdb88ce1819…3f68ca
Audit this contract →
← previous block
·
next block →
recent activity