pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,706,463
← previous block
next block →
recent activity
Analyzing
Block #87,706,463
13 transactions · 12 stateful · 2026-07-14 13:12:21 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,706,463
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
0xab083028
#3
0x0c7abd22
#4
0x98717539
#5
execFwdPositionOps
#6
0x3f5c179b
· blocks 1
#7
closeTrade
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
setData
#12
execOrders
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xa1bfcc4c…f2db
0x851145…3f07
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xad436b12…f632
0x1111b3…4111
2 touches
0 conflicts
0xb7c8652f…ebce
0x1111b3…4111
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
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:
0x851145ea…9f3f07
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity