pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#87,256,943
← previous block
next block →
recent activity
Analyzing
Block #87,256,943
9 transactions · 8 stateful · 2026-07-12 11:05:33 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,256,943
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
#5
0x5339c59f
#7
0x6a537575
#8
setData
#4
0x0f6795d9
· blocks 1
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1aa5ecc1…1b3d
0x34b655…2a6f
2 touches
0 conflicts
0x3f13b2ab…c87a
0x34b655…2a6f
2 touches
0 conflicts
0x3f20bc12…2a09
0x34b655…2a6f
2 touches
0 conflicts
0x42dd9d36…3fc0
0x34b655…2a6f
2 touches
0 conflicts
0x64800813…db9f
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
0x93b6fab01a…2d09d6
Audit this contract →
← previous block
·
next block →
recent activity