pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,678,742
← previous block
next block →
recent activity
Analyzing
Block #86,678,742
8 transactions · 6 stateful · 2026-07-09 18:40:53 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,678,742
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
0x6a4febad
#6
setData
#7
0xae6b8a…9404
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0x38a6ef6a…4fee
0x34b655…2a6f
4 touches
1 conflict
0xfedfa14c…e9eb
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x1277f187…837c
0x34b655…2a6f
2 touches
0 conflicts
0x1a0f02e4…f207
0x34b655…2a6f
2 touches
0 conflicts
0x273c2a35…7513
0x34b655…2a6f
2 touches
0 conflicts
0x36203b4b…8a05
0x34b655…2a6f
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
0x706c758c00…e62fdb
Audit this contract →
← previous block
·
next block →
recent activity