pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,901,033
← previous block
next block →
recent activity
Analyzing
Block #97,901,033
11 transactions · 11 stateful · 2026-08-21 11:54:50 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,901,033
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
0xab083028
#3
0xab083028
#4
execute
· blocks 1
#6
transfer
· blocks 2
#9
execFwdPositionOpsV2
#10
execOrders
#5
execute
#7
transfer
· blocks 1
#8
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4e19ae4…0788
0xe7cd86…c82d
6 touches
3 conflicts
0xeaced15b…2221
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
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:
0xe7cd86e1…0fc82d
3 conflicts on slot
0xc4e19ae47e…dc0788
Audit this contract →
← previous block
·
next block →
recent activity