pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,513,036
← previous block
next block →
recent activity
Analyzing
Block #87,513,036
8 transactions · 8 stateful · 2026-07-13 15:38:09 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,513,036
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
0x5a5d9a99
· blocks 2
#6
0x6a5506d9
#7
setData
#4
0x5a5d9a99
· blocks 1
#5
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x767799cd…f423
0xc8689a…ee79
4 touches
1 conflict
0x69ce640b…884a
0x34b655…2a6f
4 touches
1 conflict
0xa2e89145…7dfa
0x34b655…2a6f
4 touches
1 conflict
0xa6dcfb9a…a491
0x34b655…2a6f
4 touches
1 conflict
0xab8066f0…e888
0x34b655…2a6f
4 touches
1 conflict
0xc82696ca…e2b3
0x34b655…2a6f
4 touches
1 conflict
0xc82f66db…833d
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
3 conflicts on slot
0x6fe7d366be…a578ff
Audit this contract →
← previous block
·
next block →
recent activity