pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,624,011
← previous block
next block →
recent activity
Analyzing
Block #86,624,011
9 transactions · 8 stateful · 2026-07-09 12:34:06 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,624,011
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#4
0x57368ddf
#6
0x0f6795d9
#7
setData
#8
0xb8024e67
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0x0fa2aa81…8170
0x34b655…2a6f
3 touches
1 conflict
0xf4705514…eed3
0x34b655…2a6f
3 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
2 touches
0 conflicts
0xaeb5864c…7679
0x2a68ba…90c5
2 touches
0 conflicts
0x7aad02c6…b979
0x34b655…2a6f
2 touches
0 conflicts
0x95591d87…400b
0x34b655…2a6f
2 touches
0 conflicts
0xa9641aa6…0c3b
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
0xafd867b7ed…d92b2d
Audit this contract →
← previous block
·
next block →
recent activity