pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,160,574
← previous block
next block →
recent activity
Analyzing
Block #85,160,574
11 transactions · 11 stateful · 2026-07-02 17:51:56 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,160,574
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
fulfillAvailableAdvancedOrders
#4
0x39435dac
#5
0x0f6795d9
#6
0x3f5c179b
#7
updateDataFeedsValuesPartial
#8
0xed82b078
#9
setData
#10
0xc7e3ec2c
#2
0x6ad2e98b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x538ee025…52a0
0x40c49f…2af0
2 touches
0 conflicts
0x5ed859e1…4502
0x40c49f…2af0
2 touches
0 conflicts
0x98e1ff09…841a
0x40c49f…2af0
2 touches
0 conflicts
0xedf45e0c…b4c4
0x40c49f…2af0
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
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity