pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,248,917
← previous block
next block →
recent activity
Analyzing
Block #84,248,917
11 transactions · 10 stateful · 2026-06-28 12:32:07 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,248,917
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
#2
0xab083028
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
transfer
· blocks 1
#9
setData
#10
0x39435dac
#5
0x0f6795d9
#8
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9df6ffe0…b995
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x7d10bc74…1726
0x34b655…2a6f
4 touches
1 conflict
0x94a8a151…941c
0x34b655…2a6f
4 touches
1 conflict
0x92339d95…0801
0x0000a8…8888
2 touches
0 conflicts
0x0295dbc5…2fee
0x065c9d…c394
2 touches
0 conflicts
0xb1a0dd74…f087
0x188d58…ea8e
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
0x9df6ffe055…d1b995
Audit this contract →
← previous block
·
next block →
recent activity