pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,569,021
← previous block
next block →
recent activity
Analyzing
Block #98,569,021
12 transactions · 12 stateful · 2026-08-23 20:15:21 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,569,021
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x39ecce49
· blocks 1
#4
0xab083028
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x59558d29
#8
0x5acec890
#9
0x6a8b5551
#10
setData
#11
execOrders
#3
0x39ecce49
#5
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xc9d85869…8531
0x3bd359…433a
4 touches
1 conflict
0xf45a6126…89bf
0x436662…7777
4 touches
1 conflict
0x00000000…0004
0x510e44…2cd9
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x3940d757…7df8
0xe1c8b7…3022
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:
Wrapped MON (WMON)
1 conflict on slot
0x44ed742f98…3963f5
Audit this contract →
← previous block
·
next block →
recent activity