pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,177,360
← previous block
next block →
recent activity
Analyzing
Block #84,177,360
12 transactions · 11 stateful · 2026-06-28 04:35:17 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,177,360
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x98717539
· blocks 1
#6
transferWithAuthorization
#7
0x6a40a4fd
#8
setData
#9
0x39435dac
#10
0xc7e3ec2c
#11
0xc7e3ec2c
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x003e3399…a0a5
0x34b655…2a6f
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0xfebf4166…9bf2
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