pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,724,280
← previous block
next block →
recent activity
Analyzing
Block #98,724,280
11 transactions · 10 stateful · 2026-08-24 09:39:09 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,724,280
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#4
0xab083028
#5
execOrders
· blocks 1
#6
0x59558d29
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#2
0xab083028
· blocks 1
#10
execOrders
#3
0x32d01e04
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x58fb4cd2…ef29
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb64473b0…0d6f
0xc8689a…ee79
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
2 touches
0 conflicts
0xaeb5864c…7679
0x2a68ba…90c5
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:
0x40c49f17…d22af0
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity