pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,168,324
← previous block
next block →
recent activity
Analyzing
Block #85,168,324
11 transactions · 10 stateful · 2026-07-02 18:43:31 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,168,324
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x957d4ba0
· blocks 2
#4
0xab083028
#5
updateDataFeedsValuesPartial
#6
0x366fe5db
#7
forward
#8
0x0f6795d9
#9
setData
#10
0x39435dac
#2
0x957d4ba0
· blocks 1
#3
0x957d4ba0
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34443913…cbf3
0x336ed4…c59c
6 touches
3 conflicts
0x00000000…000a
0x90c374…be45
6 touches
3 conflicts
0x00000000…000b
0x90c374…be45
6 touches
3 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
4 touches
1 conflict
0x47d4745e…02bb
0x336ed4…c59c
4 touches
1 conflict
0x93c58e4d…9b32
0x336ed4…c59c
4 touches
1 conflict
0x006e55b1…660f
0x8d1565…6723
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
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:
0x336ed437…cfc59c
3 conflicts on slot
0x3444391364…9ecbf3
Audit this contract →
← previous block
·
next block →
recent activity