pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,947,145
← previous block
next block →
recent activity
Analyzing
Block #86,947,145
9 transactions · 8 stateful · 2026-07-11 00:34:26 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.56
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,947,145
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 2
#3
0x0f6795d9
· blocks 2
#6
0x57368ddf
#7
0x6a51900a
#8
setData
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecb52d36…abcf
0x34b655…2a6f
4 touches
1 conflict
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc7981744…932f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xecb52d36…abce
0x34b655…2a6f
4 touches
1 conflict
0x18e8fee8…2119
0x34b655…2a6f
4 touches
1 conflict
0x38a997a6…c97a
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
1 conflict on slot
0xecb52d36f8…37abcf
Audit this contract →
← previous block
·
next block →
recent activity