pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,563,564
← previous block
next block →
recent activity
Analyzing
Block #98,563,564
10 transactions · 9 stateful · 2026-08-23 19:46:49 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,563,564
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xbbb036a8
· blocks 2
#4
updatePrices
#5
execute
#6
0xab083028
· blocks 1
#8
updateDataFeedsValuesPartial
#9
approve
#2
0x575c0012
· blocks 1
#7
0xab083028
#3
0x575c0012
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36743f6f…476b
0x3bd359…433a
6 touches
3 conflicts
0xe31cf99d…cb66
0x754704…b603
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e018
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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:
Wrapped MON (WMON)
3 conflicts on slot
0x36743f6fc4…37476b
Audit this contract →
← previous block
·
next block →
recent activity