pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,109,775
← previous block
next block →
recent activity
Analyzing
Block #84,109,775
10 transactions · 8 stateful · 2026-06-27 21:05:30 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,109,775
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
0x98717539
#6
0xed82b078
#7
setData
#8
0x39435dac
· blocks 1
#5
0xed82b078
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x120847e2…98c2
0x34b655…2a6f
4 touches
1 conflict
0x14a1e42b…a076
0x34b655…2a6f
4 touches
1 conflict
0x15551610…9255
0x34b655…2a6f
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x3c8ef3eb…7577
0x34b655…2a6f
4 touches
1 conflict
0x5afc4280…bb91
0x34b655…2a6f
4 touches
1 conflict
0x6f1a10f8…5a04
0x34b655…2a6f
4 touches
1 conflict
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
0x120847e2b0…d298c2
Audit this contract →
← previous block
·
next block →
recent activity