pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,310,445
← previous block
next block →
recent activity
Analyzing
Block #87,310,445
10 transactions · 10 stateful · 2026-07-12 17:03:14 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
#87,310,445
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x0f6795d9
#7
0x0f6795d9
· blocks 1
#8
setData
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9001f549…089d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x0fbddd0f…7cdc
0x34b655…2a6f
2 touches
0 conflicts
0x1067498b…53a5
0x34b655…2a6f
2 touches
0 conflicts
0x3ea25e92…a36d
0x34b655…2a6f
2 touches
0 conflicts
0x69c491e3…98d9
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
0x9001f5497d…54089d
Audit this contract →
← previous block
·
next block →
recent activity