pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,914,428
← previous block
next block →
recent activity
Analyzing
Block #97,914,428
12 transactions · 10 stateful · 2026-08-21 13:03:05 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,914,428
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe33905c2
#2
matchOrders
#3
0xab083028
· blocks 2
#5
0xab083028
#6
execOrders
#7
execute
#9
0x61d59c2d
#10
0x59558d29
#11
execOrders
#4
0xab083028
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9526ab…def7
0x40c49f…2af0
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x7bed0389…2ffc
0x40c49f…2af0
4 touches
1 conflict
0xc4d98fb1…c354
0x40c49f…2af0
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
2 touches
0 conflicts
0x00000000…002e
0x59df86…2780
2 touches
0 conflicts
0x00000000…002f
0x59df86…2780
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
0xdc9526ab58…bbdef7
Audit this contract →
← previous block
·
next block →
recent activity