pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,083,216
← previous block
next block →
recent activity
Analyzing
Block #98,083,216
11 transactions · 10 stateful · 2026-08-22 03:16:57 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,083,216
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execOrders
· blocks 1
#3
0xab083028
#6
execOrder
#7
0x59558d29
#8
executeBatch
#9
execOrders
#10
0x61d59c2d
#4
execOrder
· blocks 1
#5
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd689a6a5…0d01
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc4959b9d…880d
0x34b655…2a6f
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0xd897d9b6…b2d9
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
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:
Perpl
1 conflict on slot
0xd689a6a5d6…600d01
Audit this contract →
← previous block
·
next block →
recent activity