pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,821,430
← previous block
next block →
recent activity
Analyzing
Block #85,821,430
6 transactions · 5 stateful · 2026-07-05 19:13:59 UTC
Parallelism
50
/100
Blocked
40
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,821,430
· 6 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
· blocks 2
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x39435dac
· blocks 1
#5
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3659eace…e64e
0x34b655…2a6f
6 touches
3 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x9ee31890…df58
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6009797…7f5b
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x3a20ada1…53e1
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
3 conflicts on slot
0x3659eace85…1ee64e
Audit this contract →
← previous block
·
next block →
recent activity