pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,075,465
← previous block
next block →
recent activity
Analyzing
Block #86,075,465
11 transactions · 7 stateful · 2026-07-06 23:28:28 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,075,465
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf5e395a
· blocks 1
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
0x39435dac
#5
0x39435dac
#7
0x6a4c3a94
#8
setData
#9
0xfac85c…9a36
#10
0x39435dac
#6
0x1be2fb9c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x72f202c5…b90f
0x065c9d…c394
4 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x36ce9ee8…5bc2
0x40c49f…2af0
4 touches
1 conflict
0x51ca3051…0972
0x3bd359…433a
2 touches
0 conflicts
0x5b4cd072…c461
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x614b85…a284
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity