pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,182,116
← previous block
next block →
recent activity
Analyzing
Block #84,182,116
8 transactions · 6 stateful · 2026-06-28 05:06:58 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,182,116
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#3
0x6a40ac6a
#4
setData
#6
execOrders
#7
0xc7e3ec2c
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0bac9de8…21cf
0x34b655…2a6f
2 touches
0 conflicts
0x178fe051…465a
0x34b655…2a6f
2 touches
0 conflicts
0x18aed17f…f2b7
0x34b655…2a6f
2 touches
0 conflicts
0x23eaa37b…6efc
0x34b655…2a6f
2 touches
0 conflicts
0x31772578…b10c
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
0xab86573c9c…f3682e
Audit this contract →
← previous block
·
next block →
recent activity