pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,125,736
← previous block
next block →
recent activity
Analyzing
Block #86,125,736
11 transactions · 10 stateful · 2026-07-07 05:03:51 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,125,736
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
· blocks 1
#3
updatePrices
#4
execOrders
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
setData
#9
0x6a4c892f
#10
execOrders
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
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
0x1e1338ef…5333
0x851145…3f07
4 touches
1 conflict
0x85ee74d8…ca9d
0x851145…3f07
3 touches
1 conflict
0xbc9af321…2ce4
0x851145…3f07
3 touches
1 conflict
0x1eb6f507…ce9f
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0xe24e2d26…b846
0x065c9d…c394
2 touches
0 conflicts
0xfd50af49…9e4b
0x065c9d…c394
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