pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#83,582,868
← previous block
next block →
recent activity
Analyzing
Block #83,582,868
10 transactions · 10 stateful · 2026-06-25 10:31:30 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,582,868
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x40e79b1b
· blocks 1
#6
setData
#7
0x0f6795d9
#8
0x6a3d03f9
#9
0x39435dac
#5
0x23afbff3
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
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0xc97994ec…a78d
0x065c9d…c394
4 touches
1 conflict
0xa0ff4e4e…5daa
0x065c9d…c394
3 touches
1 conflict
0x740e99c2…e927
0x065c9d…c394
3 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x09bfb36d…ad15
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x557cd4fad5…e4228c
Audit this contract →
← previous block
·
next block →
recent activity