pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,923,039
← previous block
next block →
recent activity
Analyzing
Block #85,923,039
10 transactions · 7 stateful · 2026-07-06 06:30:52 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,923,039
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x3f5c179b
#4
0x0f6795d9
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x186f88…5ab8
#9
0x39435dac
#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
0x09500602…94ea
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x08e7720e…7ab4
0x34b655…2a6f
2 touches
0 conflicts
0x1c20587c…6789
0x34b655…2a6f
2 touches
0 conflicts
0x1e437c0b…e560
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
0x0950060282…6794ea
Audit this contract →
← previous block
·
next block →
recent activity