pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,853,200
← previous block
next block →
recent activity
Analyzing
Block #97,853,200
24 transactions · 23 stateful · 2026-08-21 07:48:36 UTC
Parallelism
88
/100
Blocked
30
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,853,200
· 24 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#3
transfer
#4
execOrders
#6
execOrders
· blocks 2
#8
execOrder
· blocks 1
#12
0xaf47a8bb
#13
forward
#14
setData
#15
0x59558d29
#16
execOrders
· blocks 1
#17
execOrders
#18
execOrders
#19
execOrders
#20
execOrders
#21
execOrders
#22
execOrders
#2
0x0c7abd22
· blocks 1
#5
0xab083028
#7
execOrders
#9
execOrder
· blocks 1
#11
0x3f5c179b
#23
execOrders
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
6
w0
7
w1
8
w0
9
w1
10
w2
11
w1
16
w0
23
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbeb2a33c…cc50
0x851145…3f07
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd53220ed…473b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 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:
0x851145ea…9f3f07
1 conflict on slot
0xbeb2a33c9d…76cc50
Audit this contract →
← previous block
·
next block →
recent activity