pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,492,348
← previous block
next block →
recent activity
Analyzing
Block #86,492,348
11 transactions · 9 stateful · 2026-07-08 21:52:43 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,492,348
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6a4ec723
#3
0x39435dac
· blocks 1
#5
0x6a4ec723
#6
0x5a5d9a99
#7
updateDataFeedsValuesPartial
#8
0x0f6795d9
#9
setData
#10
0xc7e3ec2c
#4
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23e3622a…5ed9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xa05675e2…e5da
0x34b655…2a6f
4 touches
1 conflict
0xa9af9157…5a6e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x31fa2836…e006
0x34b655…2a6f
4 touches
1 conflict
0x06f242d6…9cc6
0x34b655…2a6f
3 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
0x23e3622a64…ea5ed9
Audit this contract →
← previous block
·
next block →
recent activity