pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,193,857
← previous block
next block →
recent activity
Analyzing
Block #86,193,857
12 transactions · 9 stateful · 2026-07-07 12:38:37 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.42
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,193,857
· 12 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
execOrders
#4
execOrders
#5
execOrders
#6
updateDataFeedsValuesPartial
#9
forward
#10
setData
#11
execOrders
#2
0x0c7abd22
· blocks 2
#7
0x6c05cd2b
· blocks 1
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5504f74a…6874
0x43cf54…7777
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0004
0x48c3bb…b17b
6 touches
3 conflicts
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 conflicts
0xdd43be87…f667
0xe1c8b7…3022
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 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:
0x43cf5407…d87777
3 conflicts on slot
0x5504f74acf…3a6874
Audit this contract →
← previous block
·
next block →
recent activity