pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,526,474
← previous block
next block →
recent activity
Analyzing
Block #85,526,474
7 transactions · 6 stateful · 2026-07-04 10:28:41 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,526,474
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
· blocks 1
#3
0x3f5c179b
#4
updateDataFeedsValuesPartial
#5
0x6a48e0d1
#6
setData
#2
0x4d8dc985
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5636ef5b…c11d
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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
0x2d8487d0…24c6
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x78dd91c5…f2eb
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
0x5636ef5bd2…49c11d
Audit this contract →
← previous block
·
next block →
recent activity