pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,745,274
← previous block
next block →
recent activity
Analyzing
Block #85,745,274
8 transactions · 4 stateful · 2026-07-05 10:46:54 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,745,274
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#4
setData
#5
0xd29f2a…c5f2
#6
0x92a1b1…df46
#7
0xa4ac94…62bf
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb4cb196…8c4a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x03ce88d7…ea0d
0x34b655…2a6f
2 touches
0 conflicts
0x137a69a8…8b93
0x34b655…2a6f
2 touches
0 conflicts
0x16ce6d1d…7e09
0x34b655…2a6f
2 touches
0 conflicts
0x1a590aff…1460
0x34b655…2a6f
2 touches
0 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
2 touches
0 conflicts
0x1fe92c2a…cbb1
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
0xfb4cb196b2…e68c4a
Audit this contract →
← previous block
·
next block →
recent activity