pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,914,932
← previous block
next block →
recent activity
Analyzing
Block #97,914,932
10 transactions · 9 stateful · 2026-08-21 13:05:38 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,914,932
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
· blocks 1
#2
0x41a8f47c
#4
0x6ad2e98b
· blocks 1
#6
0x0c7abd22
#7
execFwdPositionOpsV2
#8
setData
#9
0x59558d29
#3
updatePrices
#5
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xbaea7a20…dee9
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0000
0x33a247…6221
2 touches
0 conflicts
0x17341352…5aeb
0x33a247…6221
2 touches
0 conflicts
0x7167a31a…76f3
0x33a247…6221
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:
0xbb3f3cb7…74e046
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity