pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,688,553
← previous block
next block →
recent activity
Analyzing
Block #86,688,553
9 transactions · 8 stateful · 2026-07-09 19:46:25 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,688,553
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#4
0x3f5c179b
#5
0x3f5c179b
· blocks 1
#8
setData
#6
0x0f6795d9
#7
0x7c51d6cf
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x112cf8ad…6e4f
0xa6afd3…d132
4 touches
1 conflict
0x32f31691…28ef
0x34b655…2a6f
2 touches
0 conflicts
0x3719925a…83d6
0x34b655…2a6f
2 touches
0 conflicts
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x815cceda…a1c9
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity