pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,573,513
← previous block
next block →
recent activity
Analyzing
Block #85,573,513
13 transactions · 10 stateful · 2026-07-04 15:41:54 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
#85,573,513
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x77813803
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x3f5c179b
#5
0x39435dac
#6
0x6a492a3a
#7
0x8bff21…d8cc
#8
0xb641f4…a866
#9
setData
#10
0x39435dac
· blocks 1
#12
0xc7e3ec2c
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x722e7100…549a
0x2880ab…7b43
2 touches
0 conflicts
0x722e7100…549b
0x2880ab…7b43
2 touches
0 conflicts
0x84495491…599a
0x754704…b603
2 touches
0 conflicts
0x8af263e4…c173
0x754704…b603
2 touches
0 conflicts
0xc96ef8cc…ff2e
0x754704…b603
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:
Perpl
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity