pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,594,415
← previous block
next block →
recent activity
Analyzing
Block #87,594,415
10 transactions · 7 stateful · 2026-07-14 00:43:08 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,594,415
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
#2
0x39435dac
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0x0f6795d9
#7
setData
#8
0xd2fdd0…9ad6
#9
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fc40870…7ef4
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x01c969a3…227b
0x34b655…2a6f
2 touches
0 conflicts
0x0a5dbc1e…74cc
0x34b655…2a6f
2 touches
0 conflicts
0x0c364f8f…ffce
0x34b655…2a6f
2 touches
0 conflicts
0x1191dbf7…8e85
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
0x3fc40870a7…c67ef4
Audit this contract →
← previous block
·
next block →
recent activity