pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,226,132
← previous block
next block →
recent activity
Analyzing
Block #86,226,132
10 transactions · 10 stateful · 2026-07-07 16:14:10 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
#86,226,132
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x9e76c652
#7
0xed82b078
#8
0x6a4d2649
#9
setData
#3
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x469dac8d…3411
0x34b655…2a6f
4 touches
1 conflict
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
2 touches
0 conflicts
0x383205ee…b8c7
0x34b655…2a6f
2 touches
0 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
2 touches
0 conflicts
0x4461bdda…8980
0x34b655…2a6f
2 touches
0 conflicts
0xac0b4a08…faae
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
0x469dac8dcd…223411
Audit this contract →
← previous block
·
next block →
recent activity