pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,785,271
← previous block
next block →
recent activity
Analyzing
Block #85,785,271
9 transactions · 6 stateful · 2026-07-05 15:13:10 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,785,271
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x6df9e92b
#4
setData
#5
0x300f49…1cd7
#6
0x3ade3a…b950
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x54773457…b076
0x065c9d…c394
2 touches
0 conflicts
0x99c384ff…8617
0x065c9d…c394
2 touches
0 conflicts
0xda4bf378…4199
0x065c9d…c394
2 touches
0 conflicts
0x1ccfa324…0b93
0x0a917f…7777
2 touches
0 conflicts
0x44ad89ba…cf83
0x0a917f…7777
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity