pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,324,632
← previous block
next block →
recent activity
Analyzing
Block #86,324,632
13 transactions · 10 stateful · 2026-07-08 03:11:57 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,324,632
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
#2
updateDataFeedsValuesPartial
#3
0xa96df62f
#4
0x39435dac
#5
0x39435dac
#6
0x0f6795d9
#7
0x3f5c179b
· blocks 1
#8
claim
#10
forward
#11
setData
#12
0x39435dac
#9
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6b405d1c…29a4
0x851145…3f07
4 touches
1 conflict
0x2c7e7448…9500
0x0000a8…8888
2 touches
0 conflicts
0x2c7e7448…9501
0x0000a8…8888
2 touches
0 conflicts
0x5cbdceef…85ac
0x0000a8…8888
2 touches
0 conflicts
0x92339d95…0801
0x0000a8…8888
2 touches
0 conflicts
0x022ae86a…3125
0x01bff4…1071
2 touches
0 conflicts
0x11b69a7e…334e
0x01bff4…1071
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