pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,294,513
← previous block
next block →
recent activity
Analyzing
Block #87,294,513
11 transactions · 10 stateful · 2026-07-12 15:16:45 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,294,513
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xab083028
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x0f6795d9
· blocks 1
#8
0x6a53b055
#9
setData
#10
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x69c491e3…98d9
0x34b655…2a6f
4 touches
1 conflict
0xc550cc48…815d
0x34b655…2a6f
4 touches
1 conflict
0xc550cc48…815e
0x34b655…2a6f
4 touches
1 conflict
0x5f689f7f…d18e
0x34b655…2a6f
4 touches
1 conflict
0x63e6c3fa…30dc
0x34b655…2a6f
4 touches
1 conflict
0x98443afe…2028
0x34b655…2a6f
3 touches
1 conflict
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
0x4f4bdabdf3…ecffba
Audit this contract →
← previous block
·
next block →
recent activity