pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,952,297
← previous block
next block →
recent activity
Analyzing
Block #83,952,297
11 transactions · 8 stateful · 2026-06-27 03:36:20 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,952,297
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
forward
#2
0xed82b078
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
0x6a3f45ac
#6
setData
#7
0x39435dac
· blocks 1
#9
0xc7e3ec2c
#10
0xc7e3ec2c
#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
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x7a2fc410…c088
0x34b655…2a6f
4 touches
1 conflict
0x7c9d8f66…dee0
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe99ebc4d…22f9
0x34b655…2a6f
4 touches
1 conflict
0x0e9c7b55…1652
0x34b655…2a6f
4 touches
1 conflict
0x12618627…5374
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
0x157dbfb216…8d4089
Audit this contract →
← previous block
·
next block →
recent activity