pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,730,490
← previous block
next block →
recent activity
Analyzing
Block #87,730,490
10 transactions · 9 stateful · 2026-07-14 15:53:15 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,730,490
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#3
executeBatch
#4
0x0f6795d9
#5
forward
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
0x6a565be3
#9
setData
#2
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ba865dd…a249
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x5170a218…3a84
0xc8689a…ee79
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x99fb7af4…c3da
0x34b655…2a6f
4 touches
1 conflict
0x2d7ea048…d78e
0x34b655…2a6f
4 touches
1 conflict
0xbf768a2f…f453
0x34b655…2a6f
4 touches
1 conflict
0xe89cdd8c…69e7
0x34b655…2a6f
4 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
0x0ba865dd79…cca249
Audit this contract →
← previous block
·
next block →
recent activity