pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,540,164
← previous block
next block →
recent activity
Analyzing
Block #90,540,164
8 transactions · 7 stateful · 2026-07-26 17:03:37 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
#90,540,164
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x0f6795d9
· blocks 1
#4
transfer
#5
cancelTournament
#6
setData
#7
0xc7e3ec2c
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731d7308…fd26
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd02bee08…6299
0x34b655…2a6f
4 touches
1 conflict
0x16eb5040…a048
0x34b655…2a6f
2 touches
0 conflicts
0x296b498d…22e2
0x34b655…2a6f
2 touches
0 conflicts
0x296b498d…22e3
0x34b655…2a6f
2 touches
0 conflicts
0x46c64562…cd41
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
0x731d73081c…7dfd26
Audit this contract →
← previous block
·
next block →
recent activity