pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,090,548
← previous block
next block →
recent activity
Analyzing
Block #98,090,548
20 transactions · 19 stateful · 2026-08-22 03:53:50 UTC
Parallelism
90
/100
Blocked
26
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,090,548
· 20 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0xa96df62f
#3
matchOrders
#4
execOrders
#5
0xab083028
· blocks 2
#7
execOrders
#8
0x59558d29
· blocks 1
#10
executeBatch
· blocks 1
#12
setData
#13
execFwdPositionOpsV2
#14
execFwdPositionOpsV2
#15
0xed82b078
· blocks 1
#17
execute
#18
execOrders
#6
0xab083028
#9
0x59558d29
#11
executeBatch
#16
0xed82b078
#19
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
8
w0
9
w1
10
w0
11
w1
15
w0
16
w1
19
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x53502937…12f1
0xe52b14…7230
3 touches
1 conflict
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:
0xe52b1424…bb7230
1 conflict on slot
0xf79df061c7…91e005
Audit this contract →
← previous block
·
next block →
recent activity