pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,487,822
← previous block
next block →
recent activity
Analyzing
Block #86,487,822
13 transactions · 12 stateful · 2026-07-08 21:22:30 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
#86,487,822
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x000000b2
#5
0x62be7533
#6
handleOps
· blocks 1
#7
cancel
#8
0x3f5c179b
#9
setData
#10
0x39435dac
#12
jMMeC
#11
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12711b58…80f3
0x384275…7777
4 touches
1 conflict
0x1167512f…b162
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x7214fb…5853
4 touches
1 conflict
0x00000000…0003
0x7214fb…5853
4 touches
1 conflict
0x0a49c44b…4b7f
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x21d22421…0b7a
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
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:
0x3842751a…237777
1 conflict on slot
0x12711b5834…f480f3
Audit this contract →
← previous block
·
next block →
recent activity