pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,064,976
← previous block
next block →
recent activity
Analyzing
Block #98,064,976
20 transactions · 18 stateful · 2026-08-22 01:45:09 UTC
Parallelism
90
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,064,976
· 20 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x7b84f330
#3
0x7b84f330
· blocks 1
#4
matchOrders
#5
postStateList
#7
0x6ad2e98b
#8
execOrders
· blocks 1
#10
0x59558d29
#11
execPerpOps
#12
execFwdPositionOpsV2
#13
0x3f5c179b
#14
0xed82b078
#15
setData
#16
execOrders
· blocks 1
#18
0x7b84f330
#6
execOrders
#9
execOrders
#17
execOrders
#19
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
6
w1
8
w0
9
w1
16
w0
17
w1
19
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2a3648a…5515
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x316a7140…e39a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
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
0xc2a3648a1c…a25515
Audit this contract →
← previous block
·
next block →
recent activity