pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,454,862
← previous block
next block →
recent activity
Analyzing
Block #98,454,862
14 transactions · 10 stateful · 2026-08-23 10:27:28 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,454,862
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd3c7e0…c314
#2
updatePrices
· blocks 1
#4
execOrders
#5
0x6ad2e98b
#6
execOrders
#7
0x140ab6…ccde
#8
0x59558d29
#9
execOrders
#10
execFwdPositionOpsV2
#11
0x6a8acb88
#12
setData
#13
execOrders
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x037849a8…fa88
0x34b655…2a6f
2 touches
0 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x21d22421…0b7a
0x34b655…2a6f
2 touches
0 conflicts
0x37202e35…3f71
0x34b655…2a6f
2 touches
0 conflicts
0x666e475d…a6c9
0x34b655…2a6f
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