pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#89,751,669
← previous block
next block →
recent activity
Analyzing
Block #89,751,669
8 transactions · 7 stateful · 2026-07-23 22:35:09 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,751,669
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
#2
0x0f6795d9
· blocks 1
#3
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
0x6a629795
#7
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd13151…943b
0x34b655…2a6f
4 touches
1 conflict
0x1346ac01…31f2
0x34b655…2a6f
4 touches
1 conflict
0xbf47a88f…7b7e
0x34b655…2a6f
4 touches
1 conflict
0xbf47a88f…7b7f
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x54041cd1…22ce
0x34b655…2a6f
2 touches
0 conflicts
0x5af098c7…4806
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
0x8cd13151fb…49943b
Audit this contract →
← previous block
·
next block →
recent activity