pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,316,338
← previous block
next block →
recent activity
Analyzing
Block #87,316,338
8 transactions · 6 stateful · 2026-07-12 17:42:38 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,316,338
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#4
0xed82b078
#5
0x5339c59f
#6
transfer
#7
setData
#3
0x0f6795d9
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
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1515ea2e…b538
0x34b655…2a6f
2 touches
0 conflicts
0x1707526c…4789
0x34b655…2a6f
2 touches
0 conflicts
0x1b111ce2…6fed
0x34b655…2a6f
2 touches
0 conflicts
0x1bda5ba1…0d32
0x34b655…2a6f
2 touches
0 conflicts
0x1fc4dc4f…c1e5
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
0xc36fa35805…6f24cb
Audit this contract →
← previous block
·
next block →
recent activity