pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,198,281
← previous block
next block →
recent activity
Analyzing
Block #85,198,281
11 transactions · 10 stateful · 2026-07-02 22:03:01 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,198,281
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a46e08d
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
execute
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
· blocks 1
#7
setData
#8
setGlobalUPLs
#10
0xc7e3ec2c
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44564d6…bb43
0x34b655…2a6f
4 touches
1 conflict
0x7e1c758b…2f47
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0xaeb5864c…7679
0x2a68ba…90c5
2 touches
0 conflicts
0x80ccfe50…1627
0x3bd359…433a
2 touches
0 conflicts
0xf64bcb56…e3f3
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
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
0xb44564d6a3…0fbb43
Audit this contract →
← previous block
·
next block →
recent activity