pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,987,718
← previous block
next block →
recent activity
Analyzing
Block #86,987,718
10 transactions · 10 stateful · 2026-07-11 05:05:32 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,987,718
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0xab083028
#3
0x0f6795d9
· blocks 1
#5
updateDataFeedsValuesPartial
#6
forward
#7
0x6a51cf93
#8
setData
#9
0x39435dac
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd38f4e6…586c
0x34b655…2a6f
4 touches
1 conflict
0xdd38f4e6…586d
0x34b655…2a6f
4 touches
1 conflict
0x619c81de…01b4
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x0e52d81f…461e
0x34b655…2a6f
2 touches
0 conflicts
0x1941b441…5889
0x34b655…2a6f
2 touches
0 conflicts
0x45877cba…0b50
0x34b655…2a6f
2 touches
0 conflicts
0x6a6e42c5…9438
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
0xdd38f4e69f…fd586c
Audit this contract →
← previous block
·
next block →
recent activity