pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,964,164
← previous block
next block →
recent activity
Analyzing
Block #86,964,164
8 transactions · 7 stateful · 2026-07-11 02:28:12 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,964,164
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#3
0x0f6795d9
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
0x6a51aab4
#7
setData
#2
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1aa
0xb1dbf0…c0d3
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x0335ae80…8414
0xb1dbf0…c0d3
3 touches
1 conflict
0x8a35acfb…d1ab
0xb1dbf0…c0d3
3 touches
1 conflict
0x9d1bb389…c7d9
0xb1dbf0…c0d3
3 touches
1 conflict
0x42150c2e…a526
0x34b655…2a6f
2 touches
0 conflicts
0x7b3da897…b268
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
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:
0xb1dbf05f…b1c0d3
1 conflict on slot
0x8a35acfbc1…6bd1aa
Audit this contract →
← previous block
·
next block →
recent activity