pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,620,967
← previous block
next block →
recent activity
Analyzing
Block #86,620,967
8 transactions · 7 stateful · 2026-07-09 12:13:46 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,620,967
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
setData
#7
0x49ea80…f53c
#3
0x5a5d9a99
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
0x00000000…0004
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ab
0xb1dbf0…c0d3
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xb20547a5…9c03
0xb1dbf0…c0d3
3 touches
1 conflict
0xffdbc34e…2db3
0xb1dbf0…c0d3
3 touches
1 conflict
0x2b268fa9…eba2
0x34b655…2a6f
2 touches
0 conflicts
0x4c9f9071…07b4
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity