pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,610,550
← previous block
next block →
recent activity
Analyzing
Block #84,610,550
10 transactions · 8 stateful · 2026-06-30 04:43:14 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,610,550
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
0xb9bbd3ee
#7
0x0f6795d9
#8
setData
#9
0x39435dac
#2
0xab083028
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10199031…6659
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xb49d2cf2…3e3f
0x40c49f…2af0
3 touches
1 conflict
0xd8af9cfb…830d
0x40c49f…2af0
3 touches
1 conflict
0x448a363c…a731
0x40c49f…2af0
2 touches
0 conflicts
0x6e14ab40…e8a6
0x40c49f…2af0
2 touches
0 conflicts
0xbe0a34c3…e7af
0x40c49f…2af0
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:
0x40c49f17…d22af0
1 conflict on slot
0x10199031da…ad6659
Audit this contract →
← previous block
·
next block →
recent activity