pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,362,813
← previous block
next block →
recent activity
Analyzing
Block #85,362,813
12 transactions · 10 stateful · 2026-07-03 16:18:58 UTC
Parallelism
83
/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,362,813
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
#2
removeLiquidity
#3
0x957d4ba0
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updatePrices
#7
swap
#8
0xc5a04723
#9
setData
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#4
0x957d4ba0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000a
0x90c374…be45
4 touches
1 conflict
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0xc88f593e…5d93
0x336ed4…c59c
3 touches
1 conflict
0x0cdc16d9…6d0d
0x1001ff…1001
2 touches
0 conflicts
0xc6f1b3af…c97c
0x1001ff…1001
2 touches
0 conflicts
0xb1a0dd74…f087
0x188d58…ea8e
2 touches
0 conflicts
0x47d4745e…02bb
0x336ed4…c59c
2 touches
0 conflicts
0x4a870d86…79ef
0x336ed4…c59c
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:
0x90c3747c…0ebe45
1 conflict on slot
0x0000000000…00000a
Audit this contract →
← previous block
·
next block →
recent activity