pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,295,114
← previous block
next block →
recent activity
Analyzing
Block #86,295,114
12 transactions · 10 stateful · 2026-07-07 23:54:42 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,295,114
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x39435dac
#3
0x39435dac
#4
0x0f6795d9
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#8
0x3f5c179b
#9
0x26fd9eea
#10
cancel
#11
setData
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x086f580e…090c
0x851145…3f07
4 touches
1 conflict
0x5303bbe2…aac6
0x851145…3f07
4 touches
1 conflict
0xabc6fb06…1401
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
0x1b6862…e19c
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:
0x851145ea…9f3f07
1 conflict on slot
0x086f580e19…03090c
Audit this contract →
← previous block
·
next block →
recent activity