pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,697,575
← previous block
next block →
recent activity
Analyzing
Block #90,697,575
8 transactions · 8 stateful · 2026-07-27 06:15:30 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
#90,697,575
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0f6795d9
· blocks 2
#3
updateDataFeedsValuesPartial
#4
verifyOracleProofV2
#6
cancelTournament
#7
setData
#2
0x0f6795d9
· blocks 1
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fbd24c7…325b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa35509fa…5cb3
0x34b655…2a6f
4 touches
1 conflict
0x2c13dd97…2ef2
0x34b655…2a6f
4 touches
1 conflict
0x850b60c9…1b4a
0x34b655…2a6f
4 touches
1 conflict
0x5330e39b…661c
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
3 conflicts on slot
0x1fbd24c7f5…59325b
Audit this contract →
← previous block
·
next block →
recent activity