pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,205,260
← previous block
next block →
recent activity
Analyzing
Block #84,205,260
8 transactions · 7 stateful · 2026-06-28 07:41:08 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,205,260
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
#2
0x1a945f9c
#3
0x0f6795d9
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x36326531
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x6b2a6570…0e70
0x34b655…2a6f
3 touches
1 conflict
0x8edd456e…c7e3
0x0555e3…2b9c
2 touches
0 conflicts
0xa590e52f…fdfd
0x0555e3…2b9c
2 touches
0 conflicts
0x90fff2ea…f877
0x065c9d…c394
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a567
0x188d58…ea8e
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
0x9a3068dd84…9918f0
Audit this contract →
← previous block
·
next block →
recent activity