pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,989,408
← previous block
next block →
recent activity
Analyzing
Block #97,989,408
11 transactions · 10 stateful · 2026-08-21 19:24:24 UTC
Parallelism
64
/100
Blocked
30
%
Avg conflicts / tx
0.73
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,989,408
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xab083028
#3
forward
#4
execFwdPositionOpsV2
· blocks 1
#5
setData
#6
execOrders
· blocks 3
#7
execOrders
#8
execOrders
· blocks 2
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
6
w0
8
w1
9
w2
10
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000b
0x14ef59…ca7e
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
2 touches
0 conflicts
0x456ccc15…e999
0x34b655…2a6f
2 touches
0 conflicts
0x49b0842d…0a93
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
6 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity