pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,323,075
← previous block
next block →
recent activity
Analyzing
Block #98,323,075
11 transactions · 11 stateful · 2026-08-22 23:24:27 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,323,075
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
#2
0x59558d29
#3
0x928e4afa
· blocks 1
#4
updatePriceFeedsIfNecessary
#5
batchUpdate
#6
approve
#7
0x6a8a3023
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
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
0x36126dcb…ca1e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
2 touches
0 conflicts
0x07576bbc…d54b
0x34b655…2a6f
2 touches
0 conflicts
0x113616a8…99ea
0x34b655…2a6f
2 touches
0 conflicts
0x265d349b…3fc1
0x34b655…2a6f
2 touches
0 conflicts
0x2b4778cd…7e1e
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
1 conflict on slot
0xe5bb3628b5…71e5f1
Audit this contract →
← previous block
·
next block →
recent activity