pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,201,263
← previous block
next block →
recent activity
Analyzing
Block #85,201,263
10 transactions · 9 stateful · 2026-07-02 22:22:51 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,201,263
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x5a5d9a99
· blocks 1
#5
0x5a5d9a99
#6
commit
#7
setData
#8
0xc7e3ec2c
#9
0xc7e3ec2c
#4
0x5a5d9a99
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
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x2917f81e…fce6
0x34b655…2a6f
4 touches
1 conflict
0x3fde350e…8d43
0x34b655…2a6f
4 touches
1 conflict
0x4eed0a91…acd1
0x34b655…2a6f
4 touches
1 conflict
0x86f95c40…5bef
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
0x34b655…2a6f
4 touches
1 conflict
0xa9c6193a…0d27
0x34b655…2a6f
4 touches
1 conflict
0xd6418d68…bdc5
0x34b655…2a6f
4 touches
1 conflict
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: Settlement / Helper
1 conflict on slot
0x922c7ebd9c…1c6600
Audit this contract →
← previous block
·
next block →
recent activity