pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,492,464
← previous block
next block →
recent activity
Analyzing
Block #98,492,464
11 transactions · 10 stateful · 2026-08-23 13:36:59 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,492,464
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
#2
execOrders
· blocks 1
#3
0x6ad2e98b
#4
0xab083028
#5
execOrders
#6
0x3eae5b…07d9
#7
execFwdPositionOpsV2
#8
0xed82b078
#9
setData
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xfd54ff1e…93c5
0x340143…768f
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
2 touches
0 conflicts
0x5f55f2c8…8f11
0x754704…b603
2 touches
0 conflicts
0x69c8bf4a…2ed0
0x754704…b603
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
0xe5bb3628b5…71e5f1
Audit this contract →
← previous block
·
next block →
recent activity