pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,638,361
← previous block
next block →
recent activity
Analyzing
Block #83,638,361
10 transactions · 7 stateful · 2026-06-25 16:42:14 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
#83,638,361
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xf99cae99
#2
0x98717539
· blocks 1
#3
forward
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateTemporalNumericValuesV1
#8
0x0f6795d9
#9
setData
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1a76640e…5d08
0x34b655…2a6f
2 touches
0 conflicts
0x235dd62b…f416
0x34b655…2a6f
2 touches
0 conflicts
0x2ed8b457…17dd
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x6767aeb1…eabc
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
0xe99d8e683a…2ea16e
Audit this contract →
← previous block
·
next block →
recent activity